-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[tests] Update eventsvalidation tests to use intree Microsoft.Diagnostics.NETCore.Client #66110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[tests] Update eventsvalidation tests to use intree Microsoft.Diagnostics.NETCore.Client #66110
Conversation
…tics.NETCore.Client
|
@BruceForstall How can I run the |
|
/azp run runtime-coreclr jitstress |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Just triggering Once the |
|
@mdh1418 @hoyosjs The build failure is not fixed: |
|
I went too quickly, I missed that the EventPipeProvider does not have a default EventLevel, and that the keyword position is changed to be 3rd instead of second. |
|
/azp run runtime-coreclr jitstress |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@BruceForstall https://dev.azure.com/dnceng/public/_build/results?buildId=1641823&view=logs&j=db768a9e-3325-5ce3-2d52-896c40bee68a is green now. Is this still good to merge despite the other seemingly unrelated failures? |
|
Merged to unblock JIT workflows. The errors were due to AzDO artifact throttling unrelated to this PR. |
|
As long as the test build finished (it did), that's good enough for now. Of course, if these changes also cause test failures, you'll see those soon... |
Fixes #66099