chore(ci): raise verify-gate timeout 30 → 60 min for lake build#229
Open
avrabe wants to merge 1 commit into
Open
chore(ci): raise verify-gate timeout 30 → 60 min for lake build#229avrabe wants to merge 1 commit into
avrabe wants to merge 1 commit into
Conversation
After #227 reverted TEST-PROOF-LATENCY / TEST-PROOF-ARINC653 verification steps from sorry-grep to `cd proofs && lake build`, the first PR after #227 (#228 Mermaid M3) timed out the verify-gate at the 30-minute hard budget. lake build against Mathlib on a cold elan cache takes 25–35 min; the runner ran for 26 min before hitting the timeout, then GitHub killed the orphan `lake` process during job cleanup. Bumps the verify-gate job's `timeout-minutes` from 30 → 60 to give `lake build` headroom while the smithy team adds Lake build-artifact caching across runs. Once that lands, the timeout can drop toward the original 20m. The dedicated "Lean proof typecheck (lake build)" workflow has its own budget for the same step (already empirically green), so this only affects the rivet verification gate runs. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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.
Summary
PR #227 reverted
TEST-PROOF-LATENCYandTEST-PROOF-ARINC653verification artifacts from sorry-grep tocd proofs && lake build. The first PR after #227 (#228) hit the verify-gate's 30-minute hard timeout — lake build against Mathlib on a cold elan cache takes 25–35 min, and the runner was terminated at 26m with an orphanlakeprocess.This bumps
timeout-minutes: 30 → 60solake buildhas headroom.Follow-up for smithy
Lake build-artifact caching across runner runs would let this drop back toward 20m. A cache key like
lake-{runner-id}-{hash(proofs/lakefile.toml)}-{hash(proofs/lean-toolchain)}onproofs/.lake/buildwould let warm runs finish in seconds rather than 25 min.Test plan
Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com