forge test extremely low when stack trace is enable (-vvv) about foundry HOT 4 OPEN

no worries @zerosnacks

indeed I do have ETHERSCAN_API_KEY in my .env

If so, a temporary workaround is passing --offline
👌🏻

from foundry.

Possibly related: #6792 / #6791

Are these fork / integration tests? Could you perhaps share the Etherscan related settings of forge config? And the logs if you run with RUST_LOG=etherscanidentifier

from foundry.

I'm running unittests locally

here is my foundry.toml

[profile.default]
src = 'src'
out = 'out'
libs = ['node_modules', 'lib']
test = 'test'
cache_path  = 'cache_forge'
remappings = [
    "lib/an-essential-dependency/lib/openzeppelin-contracts/=node_modules/@openzeppelin/",
]

Except for the remapping is the default file created by Hardhat during init cmd: npx hardhat init-foundry

I use the remapping for a dependency that has pinned down solc version which itself relies on OpenZeppelin. But install cmd
forge install cool-creator/an-essential-dependency
init it sub-module OpenZeppelin to the latest version which is incompatible with parent solc version

ps: the delay appends on every test so if I run the whole suit with a forge test that goes from ~8s to ~240s

from foundry.

Apologies for the delay @codekoriko

Do happen to have an ETHERSCAN_API_KEY defined in a local .env?

See: #7555

If so, a temporary workaround is passing --offline

from foundry.