Skip to content

Demos Visual Tests: replace job-level always() with !cancelled() so cancel-in-progress can stop jobs - #34930

Merged
EugeniyKiyashko merged 1 commit into
DevExpress:26_1from
EugeniyKiyashko:fix/cancel_in_progress_26_1
Aug 26, 2026
Merged

EugeniyKiyashko merged 1 commit into
DevExpress:26_1from
EugeniyKiyashko:fix/cancel_in_progress_26_1

Conversation

@EugeniyKiyashko

Copy link
Copy Markdown
Contributor

No description provided.

…ancel-in-progress can stop jobs

When a workflow run is canceled (by concurrency cancel-in-progress or
manually), GitHub re-evaluates job-level if conditions and lets jobs
whose condition still holds keep running. always() holds even after
cancellation, so every heavy job survived the cancel: the superseded
run kept occupying devextreme-shr2 runners until it drained naturally,
while the new run waited in pending for the whole time.

!cancelled() behaves identically in normal flows (it overrides the
implicit success() gate the same way) but turns false once the run is
canceled, so jobs actually stop. Step-level always() (result reporting
and artifact upload steps) is intentional and left untouched.
@EugeniyKiyashko
EugeniyKiyashko merged commit c4ccedc into DevExpress:26_1 Aug 26, 2026
105 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants