Add initial release testing for outerloop and jitstress pipelines #41856
Conversation
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
I have fixed the CoreCLR outerloop pipeline to include the release branches. For jitstress and libraries_jitstress I have split the schedules to run every other day for master vs. release as with the growing number of Mono runs there's not much space for maneuver w.r.t. allocating new lab HW. Fixes: dotnet#41841 Thanks Tomas
hoyosjs
approved these changes
Sep 4, 2020
BruceForstall
approved these changes
Sep 4, 2020
safern
approved these changes
Sep 8, 2020
|
@safern - I must admit I'm somewhat confused here. When I click "Edit" on the "runtime-coreclr jitstress" pipeline definition, for instance, it claims to be using a YAML script off the "master" branch. Are you sure we need to port the change or should we loop in more people to help us clarify this? |
|
That is the "default" branch where a build would be queued and the yml that would be used. However, when you run a build from a PR branch or a CI branch, it will use the yml that is checked in on that branch. |
I have somewhat arbitrarily added a Sunday run for jitstress on release branches and for libraries-jitstress on master; I don't think I have any compelling reason for not doing it the other way round, except perhaps for a bit of symmetry in the YAML code. Thanks Tomas
|
Thanks Santi for clarifying. I'll prepare a porting request after merging this in. |
|
/backport to release/5.0-rc2 |
|
Started backporting to release/5.0-rc2: https://github.com/dotnet/runtime/actions/runs/245362567 |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I have fixed the CoreCLR outerloop pipeline to include the release
branches. For jitstress and libraries_jitstress I have split the
schedules to run every other day for master vs. release as with
the growing number of Mono runs there's not much space for maneuver
w.r.t. allocating new lab HW.
Fixes: #41841
Thanks
Tomas
P.S. There's not much I can do about validating that the updated
schedules actually work apart from just running the pipeline on the
PR to at least verify that the YAML is syntactically correct.
/cc: @dotnet/runtime-infrastructure