Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jest did not exit one second after the test run has completed. #8111

Closed
nivida opened this issue Mar 12, 2019 · 5 comments
Closed

Jest did not exit one second after the test run has completed. #8111

nivida opened this issue Mar 12, 2019 · 5 comments
Labels

Comments

@nivida
Copy link

nivida commented Mar 12, 2019

🐛 Bug Report

I've updated jest to the latest version because of the bug with NodeJS version 11.11.0. All tests do success but it prompts the following message:
"Jest did not exit one second after the test run has completed"

To Reproduce

Steps to reproduce the behavior:

  1. install the latest version of jest

Expected behavior

Tests should work as before.

Link to repl or repo (highly encouraged)

https://github.com/ethereum/web3.js

System:
    OS: macOS 10.14.3
Binaries:
    Node: 11.11.0 - ~/.nvm/versions/node/v11.11.0/bin/node
    Yarn: 1.12.1 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v11.11.0/bin/npm
npmPackages:
    jest: ^24.4.0 => 24.4.0
@abhishek-1985
Copy link

abhishek-1985 commented Mar 14, 2019

The issue is tied to node-notifier bug in 5.4 version :- mikaelbr/node-notifier#271

There is already a jest bug similar to it - #7890

@SimenB
Copy link
Member

SimenB commented Mar 14, 2019

Duplicate of #8036

@SimenB SimenB marked this as a duplicate of #8036 Mar 14, 2019
@SimenB SimenB closed this as completed Mar 14, 2019
@shirshak55
Copy link

@SimenB thanks to this issue lol it wasted my whole day later to realise notify:true on jest config was culprit lol :(

@emmanuel-isaac
Copy link

@shirshak55 Thanks for this. I thought I was going nuts. I had done every cleanup possible.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants