[image] My Coding Journey: Beginner to Pro Kept getting an error about the timeout exceeding 2000ms, so I added a quick fix that disables the timeout this.timeout(0); Hi @Jshanks21 Sorry you had this issue. Are you able to share your test and contract so that I can try to reproduce?

Hi @Jshanks21 , The default timeout in mocha is 2000ms. The first run of beforeEach I get a duration (ms) ~1200 The beforeEach is deploying a token and a smart contract so takes a little bit of time. I reproduced by adding a sleep await new Promise(r => setTimeout(r, 2000)); As you have done, yo…

OpenZeppelin Test Environment: Timeout exceeding 2000ms

Support

Jshanks21 March 5, 2020, 12:42am 10

I should be able to do that. I’ll definitely be adding it to my My Coding Journey when I do it anyway. I’ll just try to be more conscious of tracking each step.

1 Like

Topic		Replies	Views
Timeout of 2000ms exceeded using Test Environment’s fork functionality Contracts	7	2573	June 29, 2020
Tests are failing using ganache-fork with OpenZeppelin Test Environment with a timeout error Support	7	1438	April 22, 2020
Contract tests forking mainnet give async callback timeout Support	8	881	November 6, 2020
Number can only safely store up to 53 bits Support	5	2860	March 10, 2020
Openzeppelin test helpers/ Error: Invalid JSON RPC response: "" Smart Contracts	2	745	May 12, 2022

OpenZeppelin Test Environment: Timeout exceeding 2000ms

Related Topics