-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix physical promotion scenario name and a couple of bugs #85343
Fix physical promotion scenario name and a couple of bugs #85343
Conversation
This was renamed but I forgot to update these occurrences. The result is that runtime-jit-experimental is not actually running with physical promotion enabled.
Tagging subscribers to this area: @hoyosjs Issue DetailsThis was renamed but I forgot to update these occurrences. The result is that runtime-jit-experimental is not actually running with physical promotion enabled (but the stress jobs do). cc @dotnet/jit-contrib PTAL @AndyAyersMS
|
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.
Seems like testenvironment.proj should loudly fail if the scenario name isn't found
One possible solution for this would be to change |
Failures look known according to build analysis. |
/azp run runtime-jit-experimental |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-jit-experimental, runtime-coreclr jitstress, runtime-coreclr libraries-jitstress |
Azure Pipelines successfully started running 3 pipeline(s). |
runtime-jit-experimental and recent jitstress runs seem to be hitting some problems I fixed in #85323, so I I ported a couple of fixes from there to this PR. |
/azp run runtime-jit-experimental, runtime-coreclr jitstress, runtime-coreclr libraries-jitstress |
Azure Pipelines successfully started running 3 pipeline(s). |
The remaining stress failures should have been fixed with #85396, but not sure what is going on with the OSX runs. |
OSX runner seems to be having issues right now, it timed out on my PR. |
It looks like there's still some libraries-jitstress failures; opened #85426 for it (doesn't look related to physical promotion). |
This was renamed but I forgot to update these occurrences. The result is that runtime-jit-experimental is not actually running with physical promotion enabled (but the stress jobs do).
cc @dotnet/jit-contrib PTAL @AndyAyersMS
Fix #85403