DNSCHANNEL stops jest from closing

Jest does not closed himself after test finished

–detectOpenHandles suggest I need to close DNSCHANNEL manually:

Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  DNSCHANNEL

      at dns.js:333:23

But I cannot find any additonal information based on that problem.

I have async tests running supertest and jest.

    "express": "^4.16.3",
    "jest": "^23.1.0",
    "supertest": "^3.1.0",
    "pg": "^7.4.3",
    "pg-pool": "^2.0.3"

Test code

const request = require('supertest');
const app = require('server');

// close the server after each test
afterEach(async () => {
  await app.db.close();
});

const wFixture = [{
      "complexity": 3,
}];

describe('Controllers', () => {
  test('list get method', async () => {
    const response = await request(app).get('/');
    expect(response.status).toEqual(200);
    expect(response.body.count).toEqual(1);
    expect(response.body.data).toEqual(wFixture);
  });
});

[mgcrea]

Can confirm that this issue still exists, in my case it does prevent jest to exit, thus requiring --forceExit:

Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  DNSCHANNEL

      at new CacheableLookup (node_modules/cacheable-lookup/source/index.js:75:14)
      at Object.<anonymous> (node_modules/got/dist/source/core/index.js:32:24)
      at Object.<anonymous> (node_modules/got/dist/source/as-promise/types.js:14:16)

with all up-to-date versions:

- nock@13.0.4
- got@11.8.0
- jest@26.6.3
- node v14.15.0 (node@14 via brew)
- OSX 10.15.7

[linkenneth]

I’m seeing the same issue here.