-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Use normal VNs when adding NRE exception sets #76639
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsLet's see what the diffs look like. This should fix the very particular example from #76638.
|
03f6f9a
to
cfcea49
Compare
Failures look known / not related. Diffs are of the traditional kind we tend to see with more precise exception sets - more CSEing, not always a size win, and sometimes even a PerfScore loss, though not that often. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix.
Let's get this some bake time in main while we look for more evidence that it might be something we want to backport.
/azp run runtime-coreclr libraries-jitstress, runtime-coreclr jitstress |
Azure Pipelines successfully started running 2 pipeline(s). |
Coreclr jitstress failures are #76280. Libraries jitstress failures seem to be there in the baseline runs too. |
Let's see what the diffs look like.
This should fix the very particular example from #76638.