Fix CoreCLR stress pipelines that run libraries tests only#99868
Fix CoreCLR stress pipelines that run libraries tests only#99868jkoritzinsky merged 3 commits intomainfrom
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 |
|
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