Skip to content

ci: the timeout guard names itself in its first 400 bytes — the validate lane's fetch check can pass #3087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rbuergi merged 1 commit into from
Sep 2, 2026
Merged

ci: the timeout guard names itself in its first 400 bytes — the validate lane's fetch check can pass #3087

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .github/scripts/check-workflow-timeouts.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
#!/usr/bin/env python3
"""Every CI job carries a hard wall-clock cap, and the cap is at most 45 minutes.
"""check-workflow-timeouts.py — every CI job carries a hard wall-clock cap, and the cap is at most 45 minutes.

(The name on this first line is load-bearing: node-repo-validate.yml fetches this file at platform-ref and
refuses a body whose first 400 bytes do not name it — the same shape as compile-check.py's check.)

WHY THIS EXISTS (maintainer, 2026-09-02: "hard cut ci runs after 45min — we pay all this")
------------------------------------------------------------------------------------------
Expand Down
Loading