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
{{ message }}
Repository navigation
Report reason for cancellation of parallel task #1226
When two tasks run in parallel, and one fails, the other seems to be cancelled, but this cancellation is not reported explicitly.
It would be significantly clearer to users what is happening if the reason for cancellation was explicitly reported.
So for example, instead of (GitHub Actions output):
⯈lint:mypy⯈CI:testtask: Failed to run task "CI:lint": task: Failed to run task "lint:mypy": exit status 1Error: Process completed with exit code 201.
have
⯈lint:mypy⯈CI:testtask: Terminated `CI:test` because parallel running task `CI:lint` failed.task: Failed to run task "CI:lint": task: Failed to run task "lint:mypy": exit status 1Error: Process completed with exit code 201.
Reacted by Brian Milco, Huib Piguillet and Aksel Blekastad
@aucampia A recent feature "failfast" has changed the behaviour here. When set false, parallel tasks will run to completion, even if a peer fails. You might like to try that.
Solution note, save err for each task, check if errors.Is(err, contextCanceled) - in func (e *Executor) Run().
Activity
trulede commentedon Feb 8, 2026
Deps are run with:
It might be possible to arrange something with
trulede commentedon Mar 19, 2026
@aucampia A recent feature "failfast" has changed the behaviour here. When set false, parallel tasks will run to completion, even if a peer fails. You might like to try that.
Solution note, save err for each task, check if errors.Is(err, contextCanceled) - in func (e *Executor) Run().