-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Test failure BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGenerationRollover #67217
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti Issue DetailsRun: runtime-coreclr libraries-jitstress 20220327.1 Failed test:
Error message:
|
@BruceForstall this seems to be an issue caused by JIT stress, could you do a first-level triage of the test failure? |
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsRun: runtime-coreclr libraries-jitstress 20220327.1 Failed test:
Error message:
|
@tommcdon I couldn't repro locally with or without stress. And the lab job didn't repro on the next two runs. My Kusto queries aren't working to find the full test history for this, unfortunately. Most likely, it is not JitStress related, but because JitStress runs cause tests to run much more frequently (due to a large number of JitStress variations), any existing timing or other "flakiness" in the test or system is made more visible in JitStress jobs. |
Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti Issue DetailsRun: runtime-coreclr libraries-jitstress 20220327.1 Failed test:
Error message:
|
Closing as we were not able to repro the issue |
Run: runtime-coreclr libraries-jitstress 20220327.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: