fix(testPathPatterns) fix absPath breaking (#15648) #14785
nodejs.yml
on: push
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
53s
TypeScript Compatibility
5m 49s
Typecheck Examples and Tests
4m 6s
Lint
1m 51s
Validate Yarn dependencies and constraints
15s
Node LTS on Ubuntu with leak detection
47s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
14 errors and 8 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)
|
|
processChild › handles mixed structure:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:111:35)
|
|
processChild › handles functions:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
|
|
processChild › handles functions:
undefined#L0
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
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 2`
- Snapshot - 0
+ Received + 1
PASS __tests__/bar.spec.js
✓ bar
› 1 snapshot updated.
+ 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 updated from 1 test suite.
at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
|
|
Node crawler does not pick up symlinked files by default:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
|
processChild › handles circular inequality properly:
undefined#L0
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles circular inequality properly:
undefined#L0
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles circular inequality properly:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:56:35)
|
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
|
|
Node crawler does not pick up symlinked files by default:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
|
can press "p" to filter by file name:
e2e/__tests__/watchModePatterns.test.ts#L51
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "p" to filter by file name: test results 2`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.spec.js
✓ bar 1
✓ bar 2
+
+ 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.
at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)
|
|
can press "t" to filter by test name:
e2e/__tests__/watchModePatterns.test.ts#L70
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "t" to filter by test name: test results 2`
- Snapshot - 0
+ Received + 1
PASS __tests__/bar.spec.js
PASS __tests__/foo.spec.js
+ 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.
at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70:18)
|
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
macOS with shard 1/3 / Node v24.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 4/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 4/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node v24.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node v24.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|