-
Notifications
You must be signed in to change notification settings - Fork 48
add circular dependency check #153
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
Conversation
Travis tests have failedHey Gant, Node.js: nodenpm run test:ci |
Codecov Report
@@ Coverage Diff @@
## master #153 +/- ##
=======================================
Coverage 81.64% 81.64%
=======================================
Files 28 28
Lines 534 534
Branches 83 83
=======================================
Hits 436 436
Misses 66 66
Partials 32 32Continue to review full report at Codecov.
|
Travis tests have failedHey Gant, Node.js: nodenpm run test:ci |
Travis tests have failedHey Gant, Node.js: nodenpm run test:ci |
Travis tests have failedHey Gant, Node.js: nodenpm run test:ci |
Travis tests have failedHey Gant, Node.js: node |
Travis tests have failedHey Gant, Node.js: nodenpm run test:ci |
Travis tests have failedHey Gant, Node.js: nodenpm run test:ci |
| "shipit": "tsc && np", | ||
| "test": "jest && yarn test:extras", | ||
| "test:ci": "jest --ci && yarn test:extras", | ||
| "test:ci": "jest --ci --runInBand && yarn test:extras", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattathompson - this was the issue with testing on travis CI! I thought --ci would do it, but nope!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GantMan: Why does not running the specs serially cause issues on Travis? Might be a dumb question but, I'll take that risk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a dumb question. So tests are designed to be forked processes for speed, but CI stops forked processes in order to protect from people getting insane processing power on those public machines or causing fork bombs and killing the server.
Result: When Jest forks a process, the server kills it ASAP, causing closed connections before a test finishes running, resulting in an error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TLDR: The Jest process farm fights the Travis process killer and Jest loses 80% of the time causing non-deterministic testing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, wow. Thats insane. Thanks for the explanation.
No description provided.