-
Notifications
You must be signed in to change notification settings - Fork 12.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
Run cancel-outdated-builds after fully setting up the env #76018
Conversation
@bors p=100 rollup=never I'll babysit landing this PR, since the only way to check if this works (without messing up half our CI configuration) is to see if it indeed works when doing an auto build :) |
@bors r+ |
📌 Commit 19d072f has been approved by |
⌛ Testing commit 19d072f with merge c10ce7a53cb149c4c53462c24b1c18093fc1ac87... |
💥 Test timed out |
What. @bors retry |
@pietroalbini I ran into the same issue in #75916 (comment) |
☀️ Test successful - checks-actions, checks-azure |
This PR fixes #75995 not working as expected.
Due to GitHub Actions limitations the environment variables set in the build matrix definition are not added by the GHA runner, but by the
setup-environment.sh
script. Before this PR thecancel-outdated-builds
action was started before that script, so it was never able to detect the "suppression" variable added in #75995. This PR reorders the jobs to make suresetup-environment.sh
runs before the action.r? @Mark-Simulacrum