You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# if any dependencies were cancelled, that's a failure
207
+
#
208
+
# see https://docs.github.com/en/actions/reference/workflows-and-actions/expressions#always
209
+
# and https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/troubleshooting-required-status-checks#handling-skipped-but-required-checks
210
+
# for why this cannot be encoded in the job-level `if:` field
211
+
#
212
+
# TL; DR: `$REASONS`
213
+
#
214
+
# The intersection of skipped-as-success and required status checks
215
+
# creates a scenario where if you DON'T `always()` run this job, the
216
+
# status check UI will block merging and if you DO `always()` run and
217
+
# a dependency is _cancelled_ (due to a critical failure, which is
218
+
# somehow not considered a failure ¯\_(ツ)_/¯) then the critically
219
+
# failing job(s) will timeout causing a cancellation here and the
220
+
# build to succeed which we don't want (originally this was just
221
+
# 'exit 0')
222
+
if ${{ needs.test-linux-64.result == 'cancelled' ||
0 commit comments