-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Mark Runtime_121736 test as GCStressIncompatible #122064
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
Conversation
Co-authored-by: jakobbotsch <[email protected]>
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
|
PTAL @dotnet/jit-contrib |
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.
Pull request overview
This PR addresses test timeouts under GCStress by marking the JIT/opt/ObjectStackAllocation/Runtime_121736 test as GCStressIncompatible. The test contains a 10 million iteration loop that causes excessive runtime when GCStress is enabled.
- Adds
RequiresProcessIsolationproperty (required forGCStressIncompatible) - Adds
GCStressIncompatibleproperty to exclude the test from GCStress runs - Includes explanatory comments for both properties
JIT/opt/ObjectStackAllocation/Runtime_121736times out under GCStress due to its 10M iteration loop.<GCStressIncompatible>true</GCStressIncompatible>to exclude from GCStress runs<RequiresProcessIsolation>true</RequiresProcessIsolation>(required for GCStressIncompatible)Fixes #122063
Original prompt
JIT/opt/ObjectStackAllocation/Runtime_121736/Runtime_121736times out under GCStress #122063✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.