Using queue.process during test prevent jest from exiting

[palumbamboo]

Description

If queue.process appears at least once in the code executed during the tests, then jest does not exit one second after the test run has completed.

If i put await in front of queue.process(...), nothing happens. The code blocks on this instruction until Jest raises error for time expire.

I've tried several solutions, but none seems to work:

• queue.close()
• queue.process with/without async, promises or done callback
• queue.clean()
• queue.obliterate()
• increase jest waiting time
• decrease bull lock duration
• use --detectOpenHandles -> with this option jest never exits at all

Every queue event callback (like closed, cleaned, drained, ...) is correctly fired. Jobs are correctly executed. Everything with Bull seems to work fine. The only problem is with queue.process(...) method.

Minimal, Working Test code to reproduce the issue.

(An easy to reproduce test case will dramatically decrease the resolution time.)

import Queue from 'bull'

describe('simple-test', () => {
  it('breaking-process-test', async () => {
    const queue = new Queue('test-queue')

    queue.process((job, done) => done())
    await queue.add({data: 'hello world'})

    expect(1).toBeTruthy()

    await queue.close()
  })
})

Bull version

^4.2.0

Additional information

NodeJs Version: 14.18.1
Jest Version: ^27.4.5

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[longhoangwkm]

I got it too

[oyatek]

me too :(

[yongkangc]

same here

[manast]

I think BullMQ supports Jest now, but unless somebody provides a PR with a fix for Bull this issue will most likely remain unresolved.

[melalj]

Any update on this?

[rohit-uf]

Also got this error.
running with the --detectOpenHandles pinpoints to the following location in code

node_modules/ioredis/built/connectors/StandaloneConnector.js:44:21