Disable gcstress and jitstress for tracing tests#85186
Merged
davmason merged 2 commits intodotnet:mainfrom Apr 25, 2023
Merged
Conversation
hoyosjs
approved these changes
Apr 23, 2023
ghost
locked as resolved and limited conversation to collaborators
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tracing tests time out pretty reliably if run under GCStress or JITStress, especially on arm or x86 platforms. We have one by one disabled most tests, but since the issues keep being filed for the remaining tests it is time to admit that they are not interesting and cause us more trouble than they're worth in the stress modes.
Fixes #84555
Fixes #83015
Fixes #80767