For some reason our test fail due to timeouts on seemingly random cli tests. This instability has been growing worse. I've spent the better part of the last two days looking into the issue without a resolution. I'm starting to think it's an artefact cause by the virtualisation used in CI, potentially related to resources starvation. The specs that fail do so trying to spawn a child process. The process never spawns eventually resulting in a timeout. This is why @nschonni attempt at addressing this by increasing the timeout in Since the spawn failure is random, and catastrophic the best solution I can think of in the short-medium term is to instruct mocha to retry failing tests individually a couple times. I've scoped this behaviour to the cli specs because at the moment we have some specs that are not reentrant.
| Name |
Last commit
|
Last update |
|---|---|---|
| bin | Loading commit data... | |
| lib | Loading commit data... | |
| media | Loading commit data... | |
| scripts | Loading commit data... | |
| src | Loading commit data... | |
| test | Loading commit data... | |
| .editorconfig | Loading commit data... | |
| .eslintrc | Loading commit data... | |
| .gitattributes | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .gitmodules | Loading commit data... | |
| .jshintignore | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| ISSUE_TEMPLATE.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| TROUBLESHOOTING.md | Loading commit data... | |
| appveyor.yml | Loading commit data... | |
| binding.gyp | Loading commit data... | |
| package.json | Loading commit data... |