-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Use dot-reporter instead of silent-reporter on CI #6653
Conversation
We need the same for Circle, it has the same 10 minute timeout |
Or maybe use some kind of dot reporter instead of silent ¯_(ツ)_/¯ |
I'd prefer that actually - it's nice seeing the progress |
Took one from the wild, looks ok locally. Let's see it on CI |
Yeah, not the best I've ever seen :P |
Crazy line wrap, but should be fine |
Yay! This one works on Travis :) |
Codecov Report
@@ Coverage Diff @@
## master #6653 +/- ##
=======================================
Coverage 63.73% 63.73%
=======================================
Files 235 235
Lines 8940 8940
Branches 3 3
=======================================
Hits 5698 5698
Misses 3241 3241
Partials 1 1 Continue to review full report at Codecov.
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
EDIT: let's switch to dot reporter instead of silent, cc @rickhanlonii.
Our test suite is getting heavier and since we're using
jest-silent-reporter
, Travis detects it as stalled build (10 mins of inactive output) and fails the build. Addedtravis_wait
to extend this period to 20 mins. See their docs for details: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-receivedI think we should explore running tests concurrently on CI to speed them up.
Test plan