foundry icon indicating copy to clipboard operation
foundry copied to clipboard

arbitrium fork test get's stuck after compilation even when tried with multiple rpc's

Open viraj124 opened this issue 10 months ago • 6 comments

Component

Forge

Have you ensured that all of these are up to date?

  • [X] Foundry
  • [X] Foundryup

What version of Foundry are you on?

forge 0.2.0 (1ca9b85 2024-04-15T02:39:24.309564000Z)

What command(s) is the bug in?

forge test

Operating System

macOS (Intel)

Describe the bug

Hi

I am trying to run fork tests and forking arb mainnet, I tried using public, infura, alchemy rpc's but my test get's stuck after compilation and I see no logs

I even set the etherscan key before running the test with ETHERSCAN_API_KEY=my_key but that didn't work too

so was wondering if there is a fix for this since my github actions also run the same tests but I don't see a problem there

thanks

viraj124 avatar Apr 15 '24 16:04 viraj124

Is it possible that you have a very big / infinite loop, or that it will just take a while? Can you see any activity when running with env RUST_LOG=debug?

DaniPopes avatar Apr 15 '24 17:04 DaniPopes

RUST_LOG=debug

no loop as soon as I remove vm.createSelectFork("my rpc"); the test executes and I see the logs

viraj124 avatar Apr 15 '24 17:04 viraj124

also don't see any logs with RUST_LOG=debug

viraj124 avatar Apr 15 '24 17:04 viraj124

I face this issue sometimes not all times for some reason

viraj124 avatar Apr 15 '24 17:04 viraj124

With what level of verbosity are you running your test? Does lowering the level (from -vvv to -vv) have an impact on the speed of the test run?

If so, a fix has been merged earlier today related to Etherscan traces not being cached correctly that largely resolves this issue.

zerosnacks avatar Apr 15 '24 21:04 zerosnacks

With what level of verbosity are you running your test? Does lowering the level (from -vvv to -vv) have an impact on the speed of the test run?

If so, a fix has been merged earlier today related to Etherscan traces not being cached correctly that largely resolves this issue.

I am debugging a failing test so the test which passes works with -vv but the failing one is stuck again

viraj124 avatar Apr 16 '24 05:04 viraj124

Hi @viraj124 are you still experiencing issues around this?

zerosnacks avatar Jul 15 '24 12:07 zerosnacks

No

On Mon, 15 Jul 2024 at 2:19 PM, zerosnacks @.***> wrote:

Hi @viraj124 https://github.com/viraj124 are you still experiencing issues around this?

— Reply to this email directly, view it on GitHub https://github.com/foundry-rs/foundry/issues/7671#issuecomment-2228370587, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGLPO4XDAVHTI7QZUGVHRUTZMO46BAVCNFSM6AAAAABGHXQ4PWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRYGM3TANJYG4 . You are receiving this because you were mentioned.Message ID: @.***>

viraj124 avatar Jul 15 '24 18:07 viraj124