-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Separate running PAL tests out to their own jobs/steps. #91643
Conversation
…time tests templates.
…L tests job to make it easier to test
…me into paltests-separate-job
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.
It looks good, but I'd feel more confident if someone more knowledgeble in the CI yml scripts took a look too.
/azp run runtime-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Looks great to me, thanks Jeremy!
Having said that, I see that |
/azp run runtime-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
The new jobs all passed, so merging this in. |
This helps us separate the different test legs in our product that are different. Instead of including the PAL tests in the cross-job copying and the significant logic around generating work items for the src/tests test tree in Helix, create a simple dedicated job for building and running the PAL tests on each platform.