feat: make detailed errors opt-in #13617
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
14s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
19s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 10s
TypeScript Compatibility
5m 56s
Typecheck Examples and Tests
3m 46s
Lint
1m 51s
Validate Yarn dependencies and constraints
14s
Node LTS on Ubuntu with leak detection
1m 18s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
6 errors and 6 warnings
notify › does not report --notify flag:
e2e/__tests__/detectOpenHandles.ts#L111
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "Jest did not exit one second after the test run has completed.·
'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue."
at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)
|
can press "u" to update snapshots:
e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "u" to update snapshots: test results 1`
- Snapshot - 0
+ Received + 1
@@ -14,7 +14,8 @@
| ^
at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35)
› 1 snapshot failed.
+ A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
Snapshot Summary
› 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them."
at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
|
testMatch should able to match file with cjs and mjs extension:
e2e/__tests__/testMatch.test.ts#L13
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/testMatch.test.ts:13:27)
|
Custom Reporters Integration › prints reporter errors:
e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\custom-reporters-test-dir'
at rmSync (e2e/Utils.ts:105:8)
at Object.<anonymous> (e2e/__tests__/customReporters.test.ts:16:24)
|
testMatch should able to match file with cts and mts extension:
e2e/__tests__/testMatchTs.test.ts#L13
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/testMatchTs.test.ts:13:27)
|
--findRelatedTests flag › coverage configuration is applied correctly:
e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test'
at rmSync (e2e/Utils.ts:105:8)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|