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
Mocha's own CI tests appear to be unstable #4103
Comments
The watch tests have been stable since weeks/months, locally on my Windows10 and with our CI tests. There is one test with uncaught exceptions, which is unstable once upon a time. When the test servers are busy and our test run slow, then it throws errorCode 7 instead of 2. I will have a look at it next week. |
Reinstalled from scratch (
|
|
(or |
Mocha's own internal tests appear to be unstable, both in CI and in local development.
On Appveyor:
While working on #3979 (CC @craigtaub @boneskull) I have had at least two occasions where Mocha's CI tests (unrelated to my work) fail, only to succeed when I force the tests to rerun by adding an empty commit to the PR. You can see the most recent example of this here:
(empty) comparison of the two git refs
In local development:
On
master
(i.e. not my code) I ran the following to repeatedly run the watch.spec.js tests:while [ 1 ]; do node bin/mocha --timeout 10000 --slow 3750
In 5 test runs (see log below), it succeeded twice and failed three times, all for different reasons. :-/
The text was updated successfully, but these errors were encountered: