Crossgen2 composite GC stress pipeline #39949
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.
/cc @dotnet/crossgen-contrib
I have a first reasonable run at
https://dev.azure.com/dnceng/public/_build/results?buildId=746207&view=results
after I fixed the CLRTest.Crossgen2.targets script to suppress the GC stress mode for the duration of Crossgen2 compilation, otherwise it seems to me that the "dotnet" command used to run Crossgen2 silently picks up the COMPlus variable and runs Crossgen2 itself in GC stress mode, causing impractical compilation times and work item timeouts left and right. The script modification hopefully also
Fixes: #39933
Thanks
Tomas