When tests are stopped by timeout, pending promises continue execution

[4ekki]

🐛 Bug Report

When tests are stopped by timeout, pending promises continue execution

To Reproduce

Run the following test:

jest.setTimeout(3000);

beforeAll(async () => {
  await longFunction(); 
});

test("Test name", async () => {
  expect(1).toBeTruthy();
});

afterAll(async () => {
  await sleep(5000);
  console.log(3)
});

async function longFunction() {
  console.log(1);
  await sleep(5000)
  console.log(2);  
}

function sleep(ms: number) {
  return new Promise((resolve) => setTimeout(resolve, ms));
}

Actual behavior

'2' is written in console

Expected behavior

longFunction execution is stopped after 3 sec, therefore '2' is not written in console.

envinfo

λ npx envinfo --preset jest
npx: installed 1 in 1.668s

  System:
    OS: Windows 10 10.0.18362
    CPU: (8) x64 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz
  Binaries:
    Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.17.3 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: 25.1.0 => 25.1.0

[4ekki]

This often leads to Jest did not exit one second after the test run has completed. behavior and various errors. F.e., I close my logger in afterAll function and if longFunction tries to log something in this moment, network error will occur.

[thernstig]

@4ekki You missed the jest.setTimeout(3000); in the pasted example, which kind of makes it harder to understand your example since the default is 5000. Would be good if you update. I noticed that by looking at the image. Also, are you using jest-circus?

[4ekki]

@thernstig, thank you for pointing this out. For some reason, github hides everything in the same line, where triple-quote code macro starts. Added new line and it was ok=)

Yes, I use jest-circus.

[thernstig]

@4ekki No worries. Also, if you add this to the start triple single-quote it looks even nicer. Like this.

```javascript

That is why it was hidden for you, since it is actually a feature.

I also found these, do you recon this is a duplicate?
#8442
#8688
#8654 (someone trying to fix it?)

Although I like your simple repro better even with an image.

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

[4ekki]

Not stale

[16oh4]

I'm running into this issue also

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