Merged
Conversation
03ec740 to
9578df1
Compare
Audit all GitHub Actions workflow timeouts against actual run durations and consolidate from 9 different values (2, 10, 30, 40, 60, 90, 120, 230, 270) down to 4 consistent tiers: - 10 min: quick utility jobs (labels, lints, deploys, reports) - 30 min: standard CI build/test/lint, docs build - 120 min: heavy compute (benchmarks, packaging, publishing, fuzz-coverage) - 240 min: marathon fuzz runs and corpus minimization Also adds timeout-minutes to 14 jobs that previously had none (defaulting to the GitHub Actions 6-hour maximum), including sqllogic-test in CI and the fuzz corpus minimization job. Notably, fuzz-coverage was hitting its old 60-min timeout and getting cancelled on most runs — bumping to 120 fixes that. Signed-off-by: Alexander Droste <alexander.droste@protonmail.com>
9578df1 to
6199963
Compare
AdamGS
approved these changes
Apr 16, 2026
robert3005
approved these changes
Apr 16, 2026
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.
Audit all GitHub Actions workflow timeouts against actual run durations and consolidate to 4 consistent tiers:
Notably, fuzz-coverage was hitting its old 60-min timeout and getting cancelled on most runs — bumping to 120 fixes that.
Timeout tiers
Per-job breakdown
⚡ Tier 1 — 10 min
approvals.ymlcheck-approvalsbench-dispatch.ymlremove-bench-labelbench-dispatch.ymlremove-sql-labelbench.ymlcommit-metadataci.ymllint-tomlci.ymlvalidate-workflow-yamlci.ymlpython-lintci.ymlcpp-lintci.ymlffi-c-testdocs.ymldeploylabels.ymlcheck_changelog_labelpackage.ymlprepare-allpublish-benchmarks-website.ymlpublishrelease-drafter.ymlupdate_release_draftreport-fuzz-crash.ymlreportreuse.ymlreuse-checkstale.ymlclose-issuestypos.ymlspellingweb.ymlchangesweb.ymldeploy🔨 Tier 2 — 30 min
ci.ymlpython-testci.ymlpython-wheel-buildci.ymlrust-docsci.ymlbuild-rust(all matrix entries)ci.ymlcheck-min-depsci.ymlrust-lintci.ymlrust-lint-no-defaultci.ymlpublic-apici.ymlrust-coverageci.ymlrust-test-sanitizerci.ymlrust-ffi-test-sanitizerci.ymlcuda-build-lintci.ymlcuda-testci.ymlcuda-test-sanitizerci.ymlcuda-test-cudfci.ymlrust-test-other(windows/arm64)ci.ymlbuild-javaci.ymlbench-codspeed(all shards)ci.ymllicense-check-and-audit-checkci.ymlcxx-testci.ymlsqllogic-testci.ymlwasm-integrationci.ymlmirici.ymlgenerated-filesci.ymlcheck-java-publish-buildci.ymlrust-publish-dry-runclose-fixed-fuzzer-issues.ymlclose-fixedcompat-gen-upload.ymldry-runcompat-gen-upload.ymluploadcompat-validation.ymlcompat-testdocs.ymlbuildpackage.ymlprepare-java-macospackage.ymlprepare-java-linuxpublish.ymlpublish-rustpublish.ymlpublish-pythonpublish.ymlpublish-javaweb.ymlcheckweb.ymlbuild🏋️ Tier 3 — 120 min
bench-pr.ymlbenchbench.ymlbenchclaude.ymlclaudefuzz-coverage.ymlcoveragefuzzer-fix-automation.ymlattempt-fixpackage.ymlprepare-pythonrelease-binaries.ymlbuildsql-benchmarks.ymlbench🔬 Tier 4 — 240 min
run-fuzzer.ymlfuzzmax_total_time=2700s)wasm-fuzz.ymlwasm-fuzz--timeout=3h30m)minimize_fuzz_corpus_workflow.ymlminimizeAlso lowered wasmfuzz
--timeoutfrom4hto3h30mso the fuzz step itself fits within 240 min with ~30 min headroom for build/setup/teardown.Notable fixes
fuzz-coveragewas silently broken: the old 60-min timeout was being hit on 4 out of 5 recent runs (all cancelled at ~61 min). Bumping to 120 min fixes this.sqllogic-testin CI had no timeout — now set to 30 min.