Outerloop stress legs triggering on PRs they shouldn't

[jkoritzinsky]

The GCStress, JITStress, and outerloop legs look to be triggering on PRs they shouldn't.

#69825

cc: @dotnet/runtime-infrastructure if there were any changes we made. @dotnet/dnceng if this is an AzDO issue we need to report.

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The GCStress, JITStress, and outerloop legs look to be triggering on PRs they shouldn't.

#69825

cc: @dotnet/runtime-infrastructure if there were any changes we made. @dotnet/dnceng if this is an AzDO issue we need to report.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[elinor-fung]

5 hours ago (#69808) was fine.
4 hours ago (#69813) was not.

[jkoritzinsky]

cc:@dotnet/dncenghot as this looks like it's an AzDO issue

[garath]

as this looks like it's an AzDO issue

Acknowledged, checking.

[MattGal]

Also tagging @agocke who touched this pipeline about 5 hours ago (

)

[agocke]

Oops, I was following security guidance, and I think I changed the PR qualifications. I'll move them back

[ericstj]

It looks like there were some more pipelines impacted: runtime-coreclr jitstress2-jitstressregs, runtime-coreclr jitstress, runtime-coreclr jitstressregs, runtime-coreclr gcstress0x3-gcstress0xc.

I've fixed all of these in the same way @agocke did to outerloop.

[ericstj]

@agocke should we cancel the builds here so that we don't waste resources? Some of these queues are now pretty deep with work that might be unnecessary.

[ericstj]

Just dropping a note here for folks who find this issue. If you see any of the mentioned builds running in your PR between the times of 10:50 AM PDT - 5:00 PM PDT you can ignore them. They are not required to pass.

[agocke]

This should be fixed now.