Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
globalTeardown not called when stopping jest via ctrl+c
See original GitHub issueHey, I want to report a bug / missing feature (depends on the point of view).
Current behavior
When you cancel jest via ctrl + c the globalTeardown hook is not called.
Minimal example https://github.com/ansgarm/jest-global-teardown-bug
Expected behavior The globalTeardown hook should be called.
Run npx envinfo --preset jest in your project directory and paste the
results here
System:
OS: macOS High Sierra 10.13.1
CPU: x64 Intel® Core™ i5-5257U CPU @ 2.70GHz
Binaries:
Node: 8.9.3 - ~/.nvm/versions/node/v8.9.3/bin/node
Yarn: 1.3.2 - ~/.yarn/bin/yarn
npm: 5.7.1 - ~/.nvm/versions/node/v8.9.3/bin/npm
npmPackages:
jest: ^22.4.3 => 22.4.3
Best! Ansgar
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:19 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
any news on this one ?
Can anyone explain why,
process.on('SIGINT', () => { console.log('SIGINT signal') })is not executed while running jest and aborting job by ctrl+c?