Jest preset not working with latest jest and jest-puppeteer about jest-puppeteer

[jsfez]

Hello @Akxe, upgrade jest to the last version to fix the error.

[Akxe]

I did the update before writing the bug report. To no avail

[jsfez]

I've taken a look at your project and was able to reproduce the bug. After updating Jest to the latest version (29.5.0) using npm install --save-dev [email protected], the issue no longer persists.

Additionally, I came across an article that may be of help in resolving similar issues. Please let us know if the bug persist.

[Akxe]

I am sorry; I am certain I did update Jest at some point, but I must have accidentally reverted it.

Would you know what this error is?

Determining test suites to run...(node:94572) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
(node:94572) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:94572) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGTERM listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:94572) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGHUP listeners added to [process]. Use emitter.setMaxListeners() to increase limit

You can update to the last dev branch or use the one with updated jest... Thanks!

[Akxe]

When I turned headless off, I saw that I am getting 23 instances of chromium for the duration of the test, yet I only have 4 active tests and 7 skipped (11 total)

I have found this issue (#269), but I am not running my tests in --watch mode

[gregberge]

Hello @Akxe, I am sorry but this issue become an "help thread". Your original issue was solved so I close it.