Skip to content

Forge test tracing does not seem to respect the Etherscan or signature caches when running tests with high verbosity #6792

Closed
foundry-rs/block-explorers
#40
@emo-eth

Description

Component

Forge

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

  • Foundry
  • Foundryup

What version of Foundry are you on?

forge 0.2.0 (293fad7 2024-01-14T00:19:24.272194000Z)

What command(s) is the bug in?

forge test

Operating System

macOS (Apple Silicon)

Describe the bug

See #6791 for more context.

Foundry appears to keep a cache of Etherscan ABIs and OpenChain signatures (at ~/.foundry/cache/etherscan/... and ~/./foundry/cache/signatures, respectively), but running tests with high verbosity on a slow internet connection results in extremely slow test runs, presumably due to pulling Etherscan/OpenChain metadata to format the traces.

It's possible that I'm misunderstanding what these caches are meant to be used for, or the root of the slow test runs issues on slow internet.

Metadata

Assignees

Labels

Type

No type

Projects

  • Status

    Completed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions