Skip to content

[Profiler] Use libddprof-based pipeline by default + cache value#2659

Merged
gleocadie merged 3 commits into
masterfrom
gleocadie/turn-on-by-default-new-profiler-pipeline
Apr 11, 2022
Merged

[Profiler] Use libddprof-based pipeline by default + cache value#2659
gleocadie merged 3 commits into
masterfrom
gleocadie/turn-on-by-default-new-profiler-pipeline

Conversation

@gleocadie

@gleocadie gleocadie commented Apr 9, 2022

Copy link
Copy Markdown
Collaborator

Summary of changes

Reason for change

Libddprof-based pipeline is the new pipeline. It has been tested and validated for a long time.

Implementation details

Change the default configuration value.

Test coverage

Other details

@gleocadie gleocadie added the area:profiler Issues related to the continous-profiler label Apr 9, 2022
@gleocadie
gleocadie force-pushed the gleocadie/turn-on-by-default-new-profiler-pipeline branch from f5e139b to c093bf1 Compare April 11, 2022 06:29
@gleocadie
gleocadie marked this pull request as ready for review April 11, 2022 06:35
@gleocadie
gleocadie requested a review from a team as a code owner April 11, 2022 06:35
@gleocadie
gleocadie merged commit 25c0025 into master Apr 11, 2022
@gleocadie
gleocadie deleted the gleocadie/turn-on-by-default-new-profiler-pipeline branch April 11, 2022 10:55
@github-actions github-actions Bot added this to the vNext milestone Apr 11, 2022
public void CheckSmoke(string appName, string framework, string appAssembly)
{
using var runner = new SmokeTestRunner(appName, framework, appAssembly, _output);
using var runner = new SmokeTestRunner(appName, framework, appAssembly, _output, enableNewPipeline: false);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we test with the new pipeline?

}

public SmokeTestRunner(string appName, string framework, string appAssembly, string commandLine, ITestOutputHelper output, bool enabledNewPipeline = false)
public SmokeTestRunner(string appName, string framework, string appAssembly, string commandLine, ITestOutputHelper output, bool enableNewPipeline = false)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we test with the new pipeline by default?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not needed since we will soon remove the code

public void CheckSmoke(string appName, string framework, string appAssembly)
{
using var runner = new SmokeTestRunner(appName, framework, appAssembly, _output);
using var runner = new SmokeTestRunner(appName, framework, appAssembly, _output, enableNewPipeline: false);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we test with the new pipeline?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

already done ... look farther in the file :P

public void CheckSmoke(string appName, string framework, string appAssembly)
{
using var runner = new SmokeTestRunner(appName, framework, appAssembly, _output, enableNewPipeline: true);
using var runner = new SmokeTestRunner(appName, framework, appAssembly, _output, enableNewPipeline: false);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

EnableNewPipeline parameter could be removed if, in SmokeTestRunner.cs, it takes true as default value. That way, this parameter should only appear if its value is set to false. And in the future, it should even disappear.
This applies to all xxxTest.cs files of that review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:profiler Issues related to the continous-profiler

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants