-
Notifications
You must be signed in to change notification settings - Fork 2k
Mocha intermittent timeouts #955
Comments
SGTM |
Hi @mleanos, I'm ok with having a global one per the entire test suite as well. |
@lirantal Ok great. Because I'm currently getting frustrated since I'm testing the tests atm :) |
Shouldn't this be about creating a sandbox for every test and making sure no requests or timeouts are running after every single test-suite finished rather than just increasing the timeout? |
@bastianwegge Can provide an example, or proposed alternative solution? I realize that my proposal may be just a temp solution. Right now, these timeouts are reaking havoc on the Travis builds, so it would be nice to get something out quickly. |
"testing the tests" - that's nice :) |
Added a timeout of 10000 ms to each server test file. This is an attempt to solve the timeout issues that we're experiencing with the Mocha tests. Especially, this is hoping to address the build fails that are caused by such timeouts. Issue is described in meanjs/mean#955
Added a timeout of 10000 ms to each server test file. This is an attempt to solve the timeout issues that we're experiencing with the Mocha tests. Especially, this is hoping to address the build fails that are caused by such timeouts. Issue is described in meanjs/mean#955
We seem to be having intermittent issues with the Mocha tests timing out; including the Travis CI builds failing due to these timeouts. This has been disrupting the flow of contributions with our PR's builds failing. Personally, when I've committed changes to a PR, I have been crossing my fingers that no tests timeout.
I suggest to implement suite level timeout increases; described here http://mochajs.org/#timeouts. This could be a permanent or temporary solution. Either way, it may save us a lot of headache when running through the CI builds.
I have a branch that I've been testing this with, and it seems to have solved the issue with timeouts. I'm setting the timeout using
this.timeout(10000);
for each server test suite (just once per file). It's a small change to each server test file.I wanted to open the discussion before I submitted a PR. Perhaps there is a bigger issue at play here, rather than just latency issues. Any thoughts, or concerns over this approach?
@lirantal @ilanbiala @codydaig @rhutchison @trainerbill @simison @bastianwegge @jloveland
The text was updated successfully, but these errors were encountered: