Repository navigation
Conversation
Labeling a pull request triggers a pull_request_target run, which joined the workflow's concurrency group and cancelled the run waiting for the GitLab pipeline, before its own job was skipped (only fork PRs act on a label). Same-repo PRs that were labeled thus never got an LTS result. Taking the group on the job only lets runs that do something join it.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #722 +/- ##
==========================================
+ Coverage 83.13% 83.48% +0.35%
==========================================
Files 52 51 -1
Lines 4376 4263 -113
==========================================
- Hits 3638 3559 -79
+ Misses 738 704 -34 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
Author
michel2323
added a commit
that referenced
this pull request
Oct 20, 2026
#726) alcf.yml no longer keeps a runner polling the Aurora pipeline for hours. It starts the pipeline as before and sets the commit status `ALCF / LTS stack (Aurora)` to pending; alcf-report.yml (restored) sets the result when GitLab's pipeline webhook dispatches it. Jobs that fail without running their script (no Aurora runner online, stuck_pending_no_matching_runners; a PBS job the runner lost, no_updates_running; runner errors) say nothing about the change. Such a pipeline is retried once with a fresh pipeline, and reported as an error that names the infrastructure failure if that fails too, instead of as a test failure. The concurrency group moves to the job, so that a labeled same-repo PR no longer cancels its own run (supersedes #722).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Labeling a pull request triggers a
pull_request_targetrun of the ALCF workflow. That run joined the workflow-level concurrency groupalcf-<PR>and cancelled thepull_requestrun waiting for the GitLab pipeline, and only then skipped its own job, since only fork PRs act on a label. Same-repo PRs that get a label, including throughgh pr create --label, thus never got an LTS result. Their check shows as failed with "Canceling since a higher priority waiting request for alcf- exists". This is currently the case for #713, #716 and #720.Moving the concurrency group to the job means only runs whose job actually runs join it. Since
pull_request_targetruns use the workflow frommain, this can only be verified after merging, by labeling a PR.