[Bug]: Async function with multiple awaits never resolves when using fake timers

Version

27.2.0

Steps to reproduce

1. Clone my repo: https://github.com/srmagura/jest-timer-repro
2. yarn install
3. yarn test

Code:

import "jest";

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

function delay(duration: number): Promise<void> {
  return new Promise((resolve) => setTimeout(resolve, duration));
}

// PASS
it("delays", async () => {
  const p = delay(100);
  jest.runAllTimers();

  expect(await p).toBeUndefined();
});

// PASS
it("delays once in a function", async () => {
  async function f(): Promise<void> {
    await delay(100);
  }

  const p = f();
  jest.runAllTimers();

  expect(await p).toBeUndefined();
});

// FAIL: Exceeded timeout of 5000 ms for a test.
it("delays twice in a function", async () => {
  async function f(): Promise<void> {
    await delay(100);
    await delay(100);
  }

  const p = f();
  jest.runAllTimers();
  jest.runAllTimers();
  jest.runAllTimers();
  jest.runAllTimers();

  expect(await p).toBeUndefined();
});

// PASS
it("delays twice in a function using real timers", async () => {
  jest.useRealTimers();

  async function f(): Promise<void> {
    await delay(100);
    await delay(100);
  }

  const p = f();
  expect(await p).toBeUndefined();
});

Expected behavior

I expect all tests to pass. In the third test, jest.runAllTimers should cause both delays to complete, and the promise returned by f should resolve.

Actual behavior

The third test fails with

thrown: "Exceeded timeout of 5000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

Additional context

The result is same when using jest.useFakeTimers('legacy').

Environment

System:
    OS: Windows 10 10.0.19043
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor            
  Binaries:
    Node: 14.17.6 - C:\Program Files\nodejs\node.EXE
    Yarn: 3.0.2 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.23.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: ^27.2.0 => 27.2.0

[nikopavlica]

This could be solvable if jest exposed the async counterparts of @sinonjs/fake-timers methods - the 'modern' implementation of fake timers.

Until that happens, it can be solved by using fake-timers directly:

const FakeTimers = require('@sinonjs/fake-timers');
const clock = FakeTimers.install();

it("delays twice in a function", async () => {
    async function f(): Promise<void> {
        await delay(100);
        await delay(100);
    }

    const p = f();
    await clock.runAllAsync(); // note the async method

    expect(await p).toBeUndefined();
});

[SimenB]

OP is fixed via #12572 by using advanceTimers: true. Available in https://github.com/facebook/jest/releases/tag/v28.0.0-alpha.8