Repository navigation
ci: bound workflow jobs with explicit timeouts - #387
Merged
Merged
Conversation
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.
Description
Bound all 13 workflow jobs so a hung command cannot consume the default six hours. Build, OS tests, action tests and CodeQL have 20 minutes; release/image work has 30; the two devcontainer builds share 45; Pages, release installation and cleanup use smaller limits. The successful Go run 43879513905 took roughly 30 seconds to 3 minutes per active job, leaving substantial room for cold runners.
Related Issue
Fixes #364.
Type of Change
Checklist
Ethical Considerations
Additional Information
Validated on macOS arm64 with Go 1.26.11, golangci-lint 2.15.0 and actionlint 1.7.12:
go test -race -shuffle=on ./...passes all 21 packages with tests;make lintreports 0 issues;git diff --checkpasses.AI assistance: OpenAI Codex inspected the issue and workflow timings, prepared the change, ran the checks and drafted this PR. No separate human review is claimed.