console.log is supressed when using --forceExit

[schovi]

bug

Having test like:

it('something', function() {
  console.log("I am from console.log")
  expect(true). toBeTruthy();
})

With command jest it will print

 PASS  tests/somethingjs
    ✓ something (27ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        3.848s
Ran all test suites matching "something".
  console.log tests/something.js:2
    I am from console.log

But when calling it like jest --forceExit it does not print any console.log output. We expent it to behave same as without --forceExit.

I tried 0.17.0 and 0.18.0, both with same result.

We use this flag, because on CI it wont end test process. Temporary solution is to have different taks on CI and local machine.

[thymikee]

I think this is pretty much connected: #2166

[thymikee]

Let's move the discussion there!

[mattkrick]

@thymikee this was not resolved by #2556. bumping the setTimeout to 100 fixes it, but that doesn't seem like an elegant solution. Can we re-open & discuss a proper fix?

[einnjo]

I'm seeing this exact same behavior in jest v19.0.2.

[jbdemonte]

This problem seems to be still there in v22.4.2

[SimenB]

Can someone provide a reproduction repo? If so, we'll reopen

[jbdemonte]

@SimenB Here it is: https://github.com/jbdemonte/jest-forceexit

[jbdemonte]

As explained in the readme, this seems to be due to the async process

[SimenB]

The issue here is that we have a timeout for flushing console logs in the default reporter: https://github.com/facebook/jest/blob/1eb02fd41ad6840350a5b2c0636151e2da8bcd8b/packages/jest-cli/src/reporters/default_reporter.js#L83-L86

Removing the setTimeout part prints the log in the correct place

#3895 tried to fix it, seems like it wasn't enough. Help appreciated!

EDIT: When running with --forceExit, onRunComplete is never called...

[vinczedani]

Any update on this issue?
I am seeing this today. jest version 24.9.0
Edit: updated jest to 26.0.1, same with this version

[github-actions]

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 30 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.