Harry Altman

Do you know what the first version that has this problem is? Thank you!

So, are you saying that the issue was in fact introduced in 5.1.50, or is 5.1.49 simply the most recent version you happened to try that worked out?

I see, OK, thanks! That gives us a place to start looking. Thanks for the report!

OK, so the most likely culprit for this seems to be that we upgraded web3 to 1.2.9...? It's not clear what we can do about this; we can't upgrade further...

Troublesome. OK, we'll have to look into this more later. Thanks for alerting us.

Is this improved any with Truffle 5.3.1? We think web3 was the source of the problem and we just upgraded that, so I'm curious whether it improved things at all.

@Arvolear, you may possibly want to use the `disableConfirmationListener` network configuration option to avoid the large number of `eth_getBlockByNumber`s. Interesting that running the tests separately is faster. That's certainly worrying....

> guys, this is getting really annoying, anything we can help with? Unfortunately this may be difficult. As best we can tell, the cause of this issue is due to...

> Disabling `disableConfirmationListener` definitely helped! Glad to hear it! > But how do you configure the default "test" network, the one that is launched as a "internal ganache" by truffle...

More environment information, from the person this happened to: OS: Release Linux Mint 20.3 Una 64-bit Kernel: Kernel Linux 5.4.0-124-generic x86_64 Desktop environment: MATE 1.26.0 Chromium version: Version 95.0.4638.54 (Official...