-
Notifications
You must be signed in to change notification settings - Fork 5.3k
More preparation for JIT\Regression test merging #79697
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
… with JIT\Regression\VS-ia64-JIT\V1.2-M02\b28077
|
Tagging subscribers to this area: @dotnet/area-system-reflection-metadata Issue Detailsnull
|
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue Detailsnull
|
|
"Build Installer Build and Test coreclr OSX_x64 Release" failure is a timeout. The entire leg ran incredibly slowly from the beginning (project restore, configuring), so I don't think it is relevant here. |
|
Note: I force pushed back to an earlier version of this change without class deduplication. The tests pass with and without, but in doing the next steps I discovered that it appears that all classes, not just the entry point ones, need to be unique. Therefore, I will be reimplementing the dedup logic. The changes here can be merged without dedup - I had simply added those since they build on this PR and (I thought) were ready. |
trylek
left a comment
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.
LGTM, thank you!
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Failures are timeouts that, as best as I can tell, are intermittent but preexisting. |
This is another collection of changes that can be merged independently of actual test merging. It may be easier to look at each commit separately. I have them collected here in order to just do one PR process, but I can split them if needed. Automated changes were done with the ILTransform tool (started by @trylek, my version at https://github.com/markples/utils/tree/for-PR-dotnet-runtime-79697, commit 6324a32f).
Remove test JIT/Regression/VS-ia64-JIT/V1.2-Beta1/b102887 - identical…
Dedup class names in GitHub_23199
Merge b399444 into one test that handles both cases
Add RequiresProcessIsolation
ILTransform -prociso<RequiresProcessIsolation>true</RequiresProcessIsolation>for any test with CLRTestTargetUnsupported, GCStressIncompatible, UnloadabilityIncompatible, JitOptimizationSensitive, TieringTestIncompatible, HeapVerifyIncompatible, IlasmRoundTripIncompatible, SynthesizedPgoIncompatible, or CrossGenTest properties.<RequiresProcessIsolation>true</RequiresProcessIsolation>for any test with CLRTestBashEnvironmentVariable, CLRTestBatchEnvironmentVariable, CLRTestEnvironmentVariable, Content, CMakeProjectReference (not sure about the last two, but they only impact 3 tests and can be examined later)<RequiresProcessIsolation>true</RequiresProcessIsolation>for any test that calls Environment.ExitILTransform -public
ILTransform -publicMainfor C#, whatever is marked.entrypointfor IL) to be publicManual fixes for public changes