Disable 2 memory heavy array tests for 2 distros #57108
Merged
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.
Fix #56567
We know System.Runtime OuterLoop tests began failing regularly but sporadically on Ubuntu 18.04 and SLES 15 starting the day after this change added a new such test in April
https://github.com/dotnet/runtime/pull/51548/files?diff=unified&w=1
There is already a test that allocates 1GB, which apparently was passing OK, but perhaps adding a 2nd running immediately afterwards is causing the GC to allocate more pages than it did when there was just one. My assumption is that these two distros are configured to be more aggressive with the OOM killer, or are configured with different memory, and the difference is not interesting. So, disabling the two tests for those distros.