ci: bump foundry-multi-seed timeout to 45 minutes#1719
Merged
Conversation
All 7 foundry-multi-seed jobs hit the 25-minute timeout on the first push-to-main that included compiler changes (PR #1718 merge). Each matrix entry runs the full difftest suite for a single seed, and 25 minutes is too tight on the build runner. Bumping to 45 minutes gives comfortable headroom based on observed ~25-minute runtime. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The check_verify_sync.py script validates that workflow timeouts match the spec. Update the source spec and regenerated JSON to reflect the foundry-multi-seed timeout bump from 25 to 45 minutes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
| \n### CI Failure Hints\n\nFailed jobs: `checks`\n\nCopy-paste local triage:\n```bash\nmake check\nlake build\nFOUNDRY_PROFILE=difftest forge test -vv\n``` |
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
2 participants
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
foundry-multi-seedjobtimeout-minutesfrom 25 to 45Root cause
Each
foundry-multi-seedmatrix entry runs the full difftest suite (DIFFTEST_SHARD_COUNT: 1) for a single seed on thebuildrunner. Observed runtime is ~25 minutes, exactly at the old limit. The 45-minute limit gives ~80% headroom.Test plan
🤖 Generated with Claude Code
Note
Low Risk
Low risk CI-only change that increases a single job timeout; the main impact is longer CI runtime/higher runner utilization if jobs hang rather than failing quickly.
Overview
Increases the
foundry-multi-seedjob timeout inverify.ymlfrom 25 to 45 minutes to prevent multi-seed matrix runs from being cancelled due to hitting the prior limit.Updates the workflow sync-spec artifacts (
verify_sync_spec.jsonand its source) to match the new expected timeout.Reviewed by Cursor Bugbot for commit 287b8e7. Bugbot is set up for automated code reviews on this repo. Configure here.