Consistently called async functions do not work well with fake timers

🐛 Bug Report

Consistently called async functions do not work well with fake timers.

To Reproduce

beforeEach(() => {
  jest.useFakeTimers();
});

const fn = async () => {
  console.log(1);
  await new Promise(resolve => setTimeout(() => resolve(), 10));
  console.log(2);
  await new Promise(resolve => setTimeout(() => resolve(), 10));
  console.log(3);
};

it('test', (done) => {
  fn().then(() => done());
  console.log(4);
  jest.advanceTimersByTime(10);
  console.log(5);
  jest.advanceTimersByTime(10);
});

Here is a result of execution:

yarn run v1.7.0
$ jest --env=node --verbose --resetMocks --resetModules --testMatch=**\\test.test.js
  console.log tests/unit/test.test.js:6
    1

  console.log tests/unit/test.test.js:15
    4

  console.log tests/unit/test.test.js:17
    5

  console.log tests/unit/test.test.js:8
    2

 FAIL  tests/unit/test.test.js (6.749s)
  × test (5052ms)

  ● test

    Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.

Expected behavior

The second promise should be resolved after the second timer advance. Also both of them should be resolved if I call the advanceTimersByTime function once with 20 ms param.

Run npx envinfo --preset jest

Paste the results here:

System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
  Binaries:
    Yarn: 1.7.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 5.4.2 - C:\Program Files\nodejs\npm.CMD

Jest version: 23.5.0

[BrendanBall]

this is still an issue and a workaround is discussed on stackoverflow. I think it would still be great if jest can support this usecase with fake timers

[github-actions[bot]]

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.