You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Gas Reports
You can run `./bootstrap.sh gas_report` to generate a detailed gas
report for the current state and update the gas_report.md file.
When running CI or tests with `./bootstrap.sh test`, the script will
automatically check if gas usage has changed by running `./bootstrap.sh
gas_report check`. If gas usage has changed, the test will fail and show
a diff of the changes.
If the changes in gas usage are expected and desired:
1. Review the diff shown in the output
2. Run `./bootstrap.sh gas_report` to update the gas report file
3. Commit the updated gas_report.md file
NOTE: Our gas reporting excludes certain tests due to Forge limitations:
- FeeRollupTest and MinimalFeeModelTest test suites are excluded
- testInvalidBlobHash and testInvalidBlobProof test cases are excluded
This is related to [this Foundry
issue](foundry-rs/foundry#10074).
This means that we don't report gas for blob validation (currently 50k
gas per blob, and we use 3 blobs per propose in production).
If you want to run gas reports directly with `forge`, you must use the
environment variable `FORGE_GAS_REPORT=true` instead of the
`--gas-report` flag. The `./bootstrap.sh gas_report` command does this
for you automatically.
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge Version: 1.0.0-stable Commit SHA: e144b82 Build Timestamp: 2025-02-13T20:02:34.979686000Z (1739476954) Build Profile: maxperf
What version of Foundryup are you on?
foundryup: 1.0.0
What command(s) is the bug in?
forge test --gas-report
Operating System
macOS (Apple Silicon)
Describe the bug
Example Repo https://github.com/just-mitch/forge-blob-gas-report-issue
forge test
works fine, but--gas-report
or--isolate
gives an evm revert.Seems related to #7277
Also experienced on linux amd64.
The text was updated successfully, but these errors were encountered: