-
-
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
Investigate default reporter broken output #6311
Comments
Fix: diff --git i/packages/jest-cli/src/__tests__/test_scheduler.test.js w/packages/jest-cli/src/__tests__/test_scheduler.test.js
index 6170d087..88aa761d 100644
--- i/packages/jest-cli/src/__tests__/test_scheduler.test.js
+++ w/packages/jest-cli/src/__tests__/test_scheduler.test.js
@@ -11,7 +11,7 @@
import TestScheduler from '../test_scheduler';
import SummaryReporter from '../reporters/summary_reporter';
-jest.mock('../reporters/default_reporter');
+jest.mock('../reporters/base_reporter');
const mockSerialRunner = {
isSerial: true,
runTests: jest.fn(), |
a saw it happening in other projects as well. i think ideally Jest should not allow any output break the reporter |
We'll have to intercept |
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days. |
#7900 probably |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
sometimes i see our concurrent reporter trying to print something to stdout/stderr while it's running tests and it results in broken output:
we should try to log everything that gets printed and find that piece that breaks the output
The text was updated successfully, but these errors were encountered: