feat(jest-fake-timers): Add feature to enable automatically advancing… #14111
Triggered via pull request
September 20, 2024 23:22
Status
Cancelled
Total duration
10m 1s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
21s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
21s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
34s
TypeScript Compatibility
5m 21s
Typecheck Examples and Tests
3m 53s
Lint
1m 34s
Validate Yarn dependencies and constraints
13s
Node LTS on Ubuntu with leak detection
1m 7s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
48 errors and 3 warnings
|
|
Lint:
packages/jest-runtime/src/index.ts#L2328
Delete `············`
|
Lint:
packages/jest-runtime/src/index.ts#L2329
Delete `··`
|
Lint:
packages/jest-runtime/src/index.ts#L2330
Delete `············`
|
Lint
Process completed with exit code 1.
|
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)
|
|
|
TypeScript Compatibility
Process completed with exit code 1.
|
Windows with shard 2/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 2/4 / Node v20.x
The operation was canceled.
|
Windows with shard 2/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 2/4 / Node v18.x
The operation was canceled.
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
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)
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
Windows with shard 4/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 4/4 / Node v18.x
The operation was canceled.
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
Windows with shard 3/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 3/4 / Node v22.x
The operation was canceled.
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
Windows with shard 2/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 2/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
Windows with shard 3/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 3/4 / Node v20.x
The operation was canceled.
|
Windows with shard 4/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 4/4 / Node v20.x
The operation was canceled.
|
Windows with shard 4/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 4/4 / Node v22.x
The operation was canceled.
|
Windows with shard 3/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 3/4 / Node v16.x
The operation was canceled.
|
Windows with shard 2/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 1/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
--findRelatedTests flag › coverage configuration is applied correctly:
node:internal/child_process#L511
Could not find test summary in the output.
OUTPUT:
PASS __tests__/a.test.js
✓ a (5 ms)
node:events:497
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:511:26)
at listOnTimeout (node:internal/timers:594:17)
at processTimers (node:internal/timers:529:7)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess.kill (node:internal/child_process:511:12)
[... lines matching original stack trace ...]
at processTimers (node:internal/timers:529:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v22.9.0
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:244:43)
|
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)
|
Windows with shard 2/4 / Node v22.x
The operation was canceled.
|
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 1`
- 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)
|
Windows with shard 1/4 / Node v20.x
The operation was canceled.
|
Windows with shard 4/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 4/4 / Node v16.x
The operation was canceled.
|
Windows with shard 2/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 2/4 / Node v16.x
The operation was canceled.
|
Windows with shard 3/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
Windows with shard 3/4 / Node v18.x
The operation was canceled.
|
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 1/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|