[release/5.0-rc2] Add initial release testing for outerloop and jitstress pipelines #41995
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: #41841 Thanks Tomas
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
safern
approved these changes
Sep 9, 2020
Member
safern
left a comment
safern
left a comment
There was a problem hiding this comment.
Infrastructure only change.
cc: @danmosemsft
Member
|
@jeffschwMSFT - my apologies, I'm still new to this process, should I just merge this in or are there additional steps involved? |
Member
|
Adding @mmitche to check when a good time is. We are working towards a coherent build and want to ensure it aligns with that effort. |
Member
|
Thanks Jeff! I'm certainly in no hurry about this change, I just wanted to double-check whether I'm expected or not to follow up on this somehow. |
Member
|
release/5.0-rc2 branch is closed. If this is still important it should be resubmitted against release/5.0. |
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.
Backport of #41856 to release/5.0-rc2
/cc @trylek
Customer Impact
Introduces outerloop, jitstress and libraries-jitstress testing in the release branch; no product impact.
Testing
I have verified by scrutinizing the AzDO UI that we haven't received today (Wednesday) libraries-jitstress results which seems to indicate that the split schedule works. After all, it's just weekday indices and we're using them in ten other pipelines.
Risk
Low