Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Timeout of 2000ms exceeded #122

Open
diavrank opened this issue Aug 29, 2021 · 0 comments
Open

Error: Timeout of 2000ms exceeded #122

diavrank opened this issue Aug 29, 2021 · 0 comments

Comments

@diavrank
Copy link

Hello, I got the following error when I run my unit tests:

I20210829-17:35:07.655(-5)? --------------------------------
I20210829-17:35:07.655(-5)? --- RUNNING APP SERVER TESTS ---
I20210829-17:35:07.655(-5)? --------------------------------
I20210829-17:35:07.655(-5)? 
I20210829-17:35:07.705(-5)? 
I20210829-17:35:07.706(-5)? 
I20210829-17:35:07.731(-5)?   sport.list
I20210829-17:35:09.741(-5)?     1) "before all" hook: wrappedFunction for "List sports correctly"
I20210829-17:35:09.742(-5)? 

...

I20210829-17:35:11.678(-5)?   28 passing (4s)
I20210829-17:35:11.678(-5)?   1 failing
I20210829-17:35:11.678(-5)? 
I20210829-17:35:11.678(-5)?   1) sport.list
I20210829-17:35:11.679(-5)?        "before all" hook: wrappedFunction for "List sports correctly":
I20210829-17:35:11.679(-5)?      Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
I20210829-17:35:11.679(-5)?       at listOnTimeout (internal/timers.js:557:17)
I20210829-17:35:11.679(-5)?       at processTimers (internal/timers.js:500:7)
I20210829-17:35:11.679(-5)? 
I20210829-17:35:11.679(-5)? 
I20210829-17:35:11.679(-5)? 
I20210829-17:35:11.679(-5)? Load the app in a browser to run client tests, or set the TEST_BROWSER_DRIVER environment variable. See https://github.com/meteortesting/meteor-mocha/blob/master/README.md#run-app-tests
error Command failed with exit code 1.

This error is only present for the first test, so the rest of them are passed ok. (I already tried by skipping the first one and then the error is present in the second test).

The error seems to be related to Mocha timeout, so, I am not sure from what version of meteor provoked this error, or maybe if my code grew up which could affect the performance (but i don't think so because I haven't added many features so far and tests were working well). As an alternative solution, I found in stackoverflow a solution that is increasing this timeout through an env var, so, with this meteor package I used:

MOCHA_TIMEOUT=10000 meteor test --once --full-app --driver-package meteortesting:mocha

And the error has gone. However, I have doubt if this is normal for every meteor app? or maybe there is an issue with a meteor release that provoke this?

On the other hand, I was wondering what is the average time to expect from a meteor app that has about 30-40 meteor methods? (web app is only a backend implementation because is used as an API for a react native app).

Notes:

  • Node 14.17.0
  • Meteor 2.3.5 (also tested on 2.3.4)
  • meteortesting:browser-tests@1.3.4
  • meteortesting:mocha@2.0.2
  • meteortesting:mocha-core@8.1.2
  • Mac OS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant