Repository navigation
Modernize JIT Directed merged runners - #132101
Conversation
Replace the glob-based Directed runners with explicit partitions grouped by DebugType and Optimize properties. Co-authored-by: Copilot App <[email protected]>
Co-authored-by: Copilot App <[email protected]>
Compile merge-safe C# tests directly in the property-grouped runners while preserving isolated project references and PhysicalPromotion environment settings. Co-authored-by: Copilot App <[email protected]>
Use one merged runner for each explicit DebugType/Optimize combination. Preserve process-isolated PhysicalPromotion projects where supported and compile their sources directly on mobile targets that cannot run out of process. Co-authored-by: Copilot App <[email protected]>
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Normalize empty and disabled optimization into the unoptimized variants and PdbOnly debug information into the release variants, leaving five merged runners while preserving item metadata and process isolation. Co-authored-by: Copilot App <[email protected]>
|
@EgorBo this model should be easier to add new projects to than the Regression test suite (no need to balance between the different numbered projects other than for the default config). |
Restore the omitted F# tailcall test, keep mixed-priority source variants in the inner loop, and retain optimized coverage for sources normalized into the unoptimized runner. Co-authored-by: Copilot App <[email protected]>
|
/azp run
|
Command 'run
Supported commands
See additional documentation. |
Co-authored-by: Copilot App <[email protected]>
Co-authored-by: Copilot App <[email protected]>
EgorBo
left a comment
There was a problem hiding this comment.
Nice! Is there a plan to do the same for regressions tests? We mostly touch those 🙂
PS: should we kick off some outerloop to validate that this PR didn't expose some incompatible test to jit/gc stress?
|
@EgorBo Thanks! I expect consolidating the Regression tests to be a separate follow-up; this PR establishes the explicit configuration-based pattern under Directed. I ran all five merged Directed runners locally on Windows x64 Checked under both Note This response was generated by GitHub Copilot. |
|
/ba-g unrelated wasm test failures |
The Directed JIT tests were grouped into merged runners through broad globs, which prevented eligible sources from being incrementally merged into their runners and obscured the compilation settings that determine which tests can run together.
This change:
Directed_1,Directed_2, andDirected_3projects with explicit source and project listsDirected_1,Directed_d,Directed_do,Directed_r, andDirected_roOptimizeas an unoptimizedd/rvariant and mapsDebugType=PdbOnlytests to the correspondingr/rovariant[Fact]tests as[OuterLoop]SkipLocalsInit, or assembly/module metadataThe merged runners do not infer or propagate platform metadata.
Validation
src\tests\build.cmd -Dir JIT\Directed x64 Checked -Priority 1Note
This pull request description was generated by GitHub Copilot.