--listTests with --forceExit doesn't flush the whole STDOUT

[aaronabramov]

when using --listTests --json flag together with forceExit config it might produce corrupted JSON, because the process exits before the whole STDOUT is flushed.
Since we don't run any tests in --listTests mode we should disable forceExit even if it's set to true

[rogeliog]

I've been having some trouble reproducing it... This is what I've been runningjest --listTests --json --forceExit

[aaronabramov]

@rogeliog it only happens with very large output (for me it was when the output string was longer than 16 bit or 65536 characters)
here's the node bug for it nodejs/node#784

[rogeliog]

I can help by putting the fix but I'm still having some trouble reproducing it... I printed 4.9M

[aaronabramov]

@rogeliog the original node issues says that it works synchronously on TTY terminals now, so that shouldn't reproduce in you local terminal. I was able to reproduce it by spawning a child process though

[aaronabramov]

seems like the issue is worse than i first though.
--json will always break the JSON if the output is longer than 65538 char and --forceExit is passed :(
just hit this issue on a large test run with --json flag

[trevor-bliss]

Any update for this one?

As a workaround, I'm using --outputFile to write the results to a temporary file and then doing post-processing against the file after the test run completes.

[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.