Skip to content

ci(foundry): add forge build cache + 45min timeout#123

Merged
drewstone merged 1 commit into
mainfrom
ci/foundry-runner-bump
May 7, 2026
Merged

ci(foundry): add forge build cache + 45min timeout#123
drewstone merged 1 commit into
mainfrom
ci/foundry-runner-bump

Conversation

@drewstone
Copy link
Copy Markdown
Contributor

Foundry CI has been failing on main with exit 143 (SIGTERM) at Run Forge build after ~17min — symptoms of solc OOM on the 220-file via-IR compile.

This adds:

  • actions/cache@v4 keyed on foundry.toml + soldeer.lock + src/test/script/dependencies content hashes, persisting cache/ and out/ between runs so unchanged files don't recompile.
  • timeout-minutes: 45 so future genuine timeouts surface as timeout errors rather than ambiguous SIGTERM exits.

Doesn't change runner size — keeping ubuntu-latest since I don't know if larger runners are enabled for the org. If this still OOMs even with cache, the follow-up is to switch to ubuntu-latest-l or split the build profile.

Foundry CI on main has been dying with exit 143 (SIGTERM) at the
'Run Forge build' step around 17min — symptoms consistent with
the runner OOM-killing solc on a 220-file via-IR build.

Adds an actions/cache@v4 step pinned to foundry.toml + soldeer.lock
+ src/test/script/dependencies hashes, restoring incremental
forge build state across runs. Also pins a 45min timeout so we get
a clear timeout signal instead of a generic SIGTERM if a future
build genuinely runs over.

If this still OOMs after the cache lands, next step is to switch
to a larger runner (ubuntu-latest-l) once that's enabled for the org.
@drewstone drewstone merged commit 87c2cf6 into main May 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant