-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix CoreCLR stress pipelines that run libraries tests only #99868
Conversation
Tagging subscribers to this area: @hoyosjs |
/azp run runtime-coreclr libraries-jitstress |
Azure Pipelines successfully started running 1 pipeline(s). |
I have seen "You must specify at least one target queue to send a job to helix. Use the HelixTargetQueues property or HelixTargetQueue items." error in some jobs, e.g. https://github.com/dotnet/runtime/pull/98858/checks?check_run_id=22732088742 Is this related? |
Looking at the error, that looks like more of a problem with specifying helix target queues. That would be more indicitive of a missing |
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
Fixed the extra-platforms as well |
/azp run runtime-coreclr libraries-jitstress, runtime-extra-platforms |
Azure Pipelines successfully started running 2 pipeline(s). |
@jkoritzinsky Looks like there's still a problem with the Helix correlation payload:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=605856&view=results (Not sure why the jobs aren't showing up in the "Checks" list above) |
…nfiguration as the job config when running libraries tests
/azp run runtime-coreclr outerloop,runtime-coreclr libraries-jitstress, runtime-extra-platforms |
Azure Pipelines successfully started running 3 pipeline(s). |
Fixes failures in runtime-coreclr libraries-* pipelines