You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The expectation should produce the typical expected/received message.
When an individual test fails catastrophically, the failing test should be identified to the user and the entire suite should continue with any remaining tests.
Actual behavior
Summary of all failing tests
FAIL tests/parsers.test.ts
● Test suite failed to run
TypeError: Do not know how to serialize a BigInt
at stringify (<anonymous>)
at messageParent (node_modules/jest-worker/build/workers/messageParent.js:34:19)
Test Suites: 1 failed, 46 passed, 47 total
Tests: 285 passed, 285 total
Snapshots: 0 total
Time: 9.718 s, estimated 10 s
Ran all test suites.
Please respond to my second expectation. It would have been easier for me to track down if the test name was included with the other information. Is it possible to add a catch handler inside the loop running the individual tests?
This actually fails outside of the context of a single test (it fails when jest tries to pass the test result from a separate thread/process back to the main process), so we don't know which specific test failure caused this error.
I hope to address this issue in Jest 28 (see #11467 (comment) for latest info)
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.
Version
27.4.7
Steps to reproduce
expect(BigInt(0)).not.toEqual(BigInt(0));
Expected behavior
The expectation should produce the typical expected/received message.
When an individual test fails catastrophically, the failing test should be identified to the user and the entire suite should continue with any remaining tests.
Actual behavior
Additional context
Possibly related issues:
11617 - jest-worker fails with "Do not know how to serialize a BigInt" in messageParent.ts instead of showing the actual assertion error message when there are 2 or more test suite files executing in parallel
11624 - [jest-worker]: bigInt serialization in jest-worker
Environment
System: OS: Linux 5.13 Linux Mint 20.3 (Una) CPU: (12) x64 Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz Binaries: Node: 14.19.0 - /usr/bin/node npm: 8.4.1 - /usr/bin/npm npmPackages: jest: ^27.4.7 => 27.4.7
The text was updated successfully, but these errors were encountered: