Timeout when using jest "useFakeTimers" functionality

What is the expected behavior?

When mocking timers in jest I would expect mocks to pass properly as those (to me) shouldn’t be related to network communication.

jest
  .useFakeTimers('modern')
  .setSystemTime(new Date('2020-01-01').getTime())

What is the actual behavior?

Test case hangs until the whole suite times out

Possible solution Make mocks not reliant on the passing time, or maybe provide a flag that would handle this behaviour differently?

How to reproduce the issue

import nock from 'nock'
import axios from 'axios'

jest
  .useFakeTimers('modern')
  .setSystemTime(new Date('2020-01-01').getTime())

describe('Test', () => {
  const url = 'http://www.google.com'

  
  beforeEach(() => nock(url).get('/').reply(201))
  afterEach(() => expect(nock.isDone()).toEqual(true))
  
  it('should pass this test', async () => {
    const res = await axios(url)
    expect(res.status).toEqual(201)
  })
})

Remove fake timers and the test case passes

Does the bug have a test case?

Yes, provided above

Versions

Software	Version(s)
Nock	v13.0.11
Node	v14.16.0
TypeScript	v3.9.7

[NTag]

I followed @chornos13 comment, started with the whole list into doNotFake, and removed one by one elements. The setup which is working on my computer (my setup is jest and supertest) is:

import { jest } from "@jest/globals";

jest
  .useFakeTimers({
    doNotFake: [
      "nextTick",
      "setImmediate",
      "clearImmediate",
      "setInterval",
      "clearInterval",
      "setTimeout",
      "clearTimeout",
    ],
  })
  .setSystemTime(new Date("2022-02-15"));

I don’t understand why Jest doesn’t offer a way to just change the date without mocking the universe…

[josh-meredith]

If you’re still having issues, try adding both nextTick and setImmediate to the array, this is the only way it’d work for me.

jest.useFakeTimers({ doNotFake: ['nextTick', 'setImmediate'] }).setSystemTime(new Date('2022-01-01'))