Console buffer not flushed before process exits

[dandv]

🐛 Bug Report

Because there's no documented way to abort tests if setup in beforeAll fails (#6695), I tried to process.exit(). This works, but it turns out it's impossible to log any errors (which had lead to the setup failing).

To Reproduce

Run this test with or without circus:

beforeAll(() => {
  if ('something failed') {
    const e = 'here is the error message that is not logged';


    console.error('Error:', e);
    process.exit(1);
  }
});

test('your test suite must contain at least one test', () => {
});

Expected behavior

I expect the console.error output to be visible in the terminal. Instead, I see this:

Link to repl or repo (highly encouraged)

https://repl.it/repls/JuniorJumboOmnipage

[SimenB]

This is expected behaviour. You call process.exit, so it exits. Not sure if it makes sense for us to try to do any more work here.

Seems like we might have a bug with failing lifecycle hooks though, need to investigate

[brandonchinn178]

This is expected behaviour. You call process.exit, so it exits. Not sure if it makes sense for us to try to do any more work here.

Not sure this answers the original issue. The issue is that, as a developer, I would expect that console.error displays the message to the console before the process exits. Is that not expected behavior?

[dandv]

@brandonchinn178: thanks for reviving this. I'm not super familiar with Node buffering and internals, but it seems there's generally a problem with logging anything before process.exit(). See for example this bug in Winston and this one in the Bristol logger.

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