[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…

No worries @abcoathup . Sorry for not responding sooner. I just pushed my changes to GitHub. This link should take you directly to the test file. I left a comment next to the line canceling out the error. It’s on line 19. You’ll want to comment this out or remove it to reproduce the error. Thanks fo…

Hi @Jshanks21 , I wasn’t able to reproduce on my system: node v10.19.0 npm 6.14.1 operating system: WSL on Windows 10 Would you mind sharing what your configuration is? I have line 19 commented //this.timeout(0); // Prevents 2000ms timeout error I am not reproducing the error: $ npm run tes…

No problem @abcoathup : node v10.16.3 npm 6.13.1 operating system: Windows 10 Commenting line 19 [timeout error enabled] Here’s the error I get: [timeout error] But it passes when I stop commenting line 19: [timeout pass]

Thank you @abcoathup ! I assumed it had something to do with my tests exceeding the built-in time limit. I also just assumed it was because my computer is too slow :sweat_smile:. I was actually just reading about a different issue in this thread where you recommended WSL too. I’ll definitely check i…

Hi @Jshanks21 , Great to hear that you want to contribute to OpenZeppelin Contracts. I would encourage using WSL (I am yet to try WSL2), as you face far fewer issues. The Microsoft documentation recommends using Windows Subsystem for Linux (for production): https://docs.microsoft.com/en-us/windows/…

Good to know. I’ll go through that and see if it helps with the issue. Seems like a good idea aside from the immediate issue I’m encountering though.

Let me know how you get on. You could always write up the process to get a Windows development environment setup :smile:

Hi @Jshanks21 , I have a small follow up question to help us understand the underlying issue better. Was the timeout happening consistently or only sometimes?

Hi @frangio , the timeout was consistent. Anytime I ran the tests without this.timeout(0); at the beginning of the tests, I received the error message above. I appreciate any additional feedback on this. P.S. I have not tried using WSL yet to see if it fixes the issue. Plan to try it within the nex…

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.

Topic		Replies	Views
Tests are failing using ganache-fork with OpenZeppelin Test Environment with a timeout error Support	7	1619	April 22, 2020
Timeout of 2000ms exceeded using Test Environment’s fork functionality Contracts	7	3169	June 29, 2020
Number can only safely store up to 53 bits Support	5	2984	March 10, 2020
Transaction was not mined within750 seconds, please make sure your transaction was properly sent SDK	17	5028	July 3, 2019
OpenZeppelin Test Environment, test failing Support	5	1817	May 7, 2020

OpenZeppelin Test Environment: Timeout exceeding 2000ms

Related topics