The jest suite run by make test. The test script in package.json runs jest --forceExit.
What happens
Every run on next prints jest's warning "A worker process has failed to exit gracefully and has been force exited". Some test leaves a timer or other open handle behind, and --forceExit hides it. One likely source: tests that show a flash message without the popup test helper (for example tests/walletDefects.test.js, tests/sendMax.test.js, tests/sendAmountRule.test.js) leave its two-second timer running. A test that leaves work running can fail another test file at random, as #578 did.
What should happen
The suite leaves nothing running when it finishes, so it exits on its own without --forceExit and without the warning.
Severity: minor
Definition of done
The handles left open are found and closed by the tests that open them.
--forceExit is removed from the test scripts and make test finishes without the warning.
Model: opus-5-5
Seen by the review of https://git.eeqj.de/sneak/AutistMask/pulls/582.
## Where
The jest suite run by `make test`. The test script in `package.json` runs `jest --forceExit`.
## What happens
Every run on `next` prints jest's warning "A worker process has failed to exit gracefully and has been force exited". Some test leaves a timer or other open handle behind, and `--forceExit` hides it. One likely source: tests that show a flash message without the popup test helper (for example `tests/walletDefects.test.js`, `tests/sendMax.test.js`, `tests/sendAmountRule.test.js`) leave its two-second timer running. A test that leaves work running can fail another test file at random, as https://git.eeqj.de/sneak/AutistMask/issues/578 did.
## What should happen
The suite leaves nothing running when it finishes, so it exits on its own without `--forceExit` and without the warning.
Severity: minor
## Definition of done
- [ ] The handles left open are found and closed by the tests that open them.
- [ ] `--forceExit` is removed from the test scripts and `make test` finishes without the warning.
Model: opus-5-5
clawbot
self-assigned this 2026-10-19 04:06:38 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Seen by the review of #582.
Where
The jest suite run by
make test. The test script inpackage.jsonrunsjest --forceExit.What happens
Every run on
nextprints jest's warning "A worker process has failed to exit gracefully and has been force exited". Some test leaves a timer or other open handle behind, and--forceExithides it. One likely source: tests that show a flash message without the popup test helper (for exampletests/walletDefects.test.js,tests/sendMax.test.js,tests/sendAmountRule.test.js) leave its two-second timer running. A test that leaves work running can fail another test file at random, as #578 did.What should happen
The suite leaves nothing running when it finishes, so it exits on its own without
--forceExitand without the warning.Severity: minor
Definition of done
--forceExitis removed from the test scripts andmake testfinishes without the warning.Model: opus-5-5