Skip to content

Make noop jobs timeout faster - #6187

Merged
kwryankrattiger merged 1 commit into
spack:developfrom
kwryankrattiger:rk/ci/noopjobs_faster
Aug 24, 2026
Merged

Make noop jobs timeout faster#6187
kwryankrattiger merged 1 commit into
spack:developfrom
kwryankrattiger:rk/ci/noopjobs_faster

Conversation

@kwryankrattiger

Copy link
Copy Markdown
Contributor

These are not required to pass and do nothing, set a minimal timeout.

These are not required to pass and do nothing, set a minimal timeout.

Signed-off-by: Ryan Krattiger <ryan.krattiger@kitware.com>
@spackbot-triage spackbot-triage Bot added the ci Related to CI/CD workflows and pipelines label Aug 21, 2026
@kwryankrattiger
kwryankrattiger merged commit c53c405 into spack:develop Aug 24, 2026
33 checks passed
kwryankrattiger pushed a commit to spack/spack that referenced this pull request Aug 24, 2026
This fixes GitLab job failures, such as [this
one](https://gitlab.spack.io/spack/spack-packages/-/jobs/24099711), that
have recently started happening after
spack/spack-packages#6187 shortened the timeout
for noop jobs.

In practice, what spack/spack-packages#6187 did
was make it so the vast majority of noop jobs will now fail immediately
after starting, since it usually takes more than 1 second for one of
these jobs to complete. This is fine for other noop jobs like
`no-specs-to-rebuild`, because [they set `allow_failure:
true`](https://github.com/spack/spack/blob/c3b3001ddc13b607cd1e36ad81c81c0453d6814d/lib/spack/spack/ci/gitlab.py#L454-L456).
The `wait-for-build-jobs` job does not currently set `allow_failure`, so
a timeout for that job causes the entire pipeline to be incorrectly
marked as failed.

Signed-off-by: Mike VanDenburgh <michael.vandenburgh@kitware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Related to CI/CD workflows and pipelines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants