Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitd8561a6

Browse files
ci: avoid cancelling other nightly-gauntlet jobs on failure (#16795)
I saw in a failing nightly-gauntlet that the macOS+Postgres testsfailing caused the Windows tests to get cancelled:https://github.com/coder/coder/actions/runs/13645971060There's no harm in letting the other test run, and will let us catchadditional flakes & failures. If one job fails, the whole matrix willstill fail (once the remaining tests in the matrix have completed) andthe slack notification will still be sent.[We previously made thischange](#8624) on our on-push `ci`workflow.Relevant documentation:> jobs.<job_id>.strategy.fail-fast applies to the entire matrix. Ifjobs.<job_id>.strategy.fail-fast is set to true or its expressionevaluates to true, GitHub will cancel all in-progress and queued jobs inthe matrix if any job in the matrix fails. This property defaults totrue.https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast
1 parent17ad284 commitd8561a6

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

‎.github/workflows/nightly-gauntlet.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ jobs:
2020
# even if some of the preceding steps are slow.
2121
timeout-minutes:25
2222
strategy:
23+
fail-fast:false
2324
matrix:
2425
os:
2526
-macos-latest

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp