Error: unable to parse: .../out/build-info/537f1e3b991a424923519417f7ebc3f1.json

[chief-mobius]

Bug Report: Unable to Parse Build-Info File with Hevm

Environment

• OS: macOS (M3), Docker (Ubuntu 20.04), Debian 12
• Versions:
  • forge: 0.2.0 (398ef4a 2024-11-23T00:27:34.394254000Z)
  • hevm: 0.53.0 (from GitHub Releases)

---

Steps to Reproduce

1. Install using HEVM Docs:

   curl -L https://foundry.paradigm.xyz | bash
   foundryup
   forge init demo
   cd demo
   forge build --ast
   hevm test
   

Observed Behavior

Error during hevm test

Error: unable to parse: .../out/build-info/537f1e3b991a424923519417f7ebc3f1.json

Request

Could you confirm if the issue is related to forge's build-info format compatibility with hevm or any required workaround? If additional information or debugging steps are needed, please let me know.
Maybe it have some related with hevm#491?

[elopez]

Hi, can you reproduce this on a more recent hevm build? You can get hevm builds from the main branch from the CI artifacts if you would like to test with those: https://github.com/ethereum/hevm/actions/workflows/build.yml?query=branch%3Amain

[msooseth]

Hi,

First of all, sorry for this. I tried this with the PR implement_new_cheatcodes (#567 ) and it seems to work fine. I changed test/Counter.t.sol's test_Increment to prove_Increment and then I'm getting:

$ hevm test
Checking 1 function(s) in contract test/Counter.t.sol:CounterTest
[RUNNING] prove_Increment()
   [PASS] prove_Increment

So once that PR gets merged, and the fix_prank gets merged, this issue should be resolved! Sorry again for this,

Mate

[msooseth]

Both PRs have been merged. The 0.54 is will be released this week if all goes fine. So I'm closing because thankfully, the underlying issue has been fixed, yay!

Thanks again for the bug report, it was very helpful,

Mate