feat(jest-fake-timers): Add feature to enable automatically advancing… #14137
Triggered via pull request
September 26, 2024 17:38
Status
Cancelled
Total duration
13m 2s
Artifacts
–
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
37s
TypeScript Compatibility
5m 37s
Typecheck Examples and Tests
3m 58s
Lint
1m 36s
Validate Yarn dependencies and constraints
15s
Node LTS on Ubuntu with leak detection
1m 14s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
31 errors and 4 warnings
Lint:
packages/jest-fake-timers/src/__tests__/modernFakeTimers.test.ts#L1348
Array type using 'number[]' is forbidden. Use 'Array<number>' instead
|
Lint:
packages/jest-fake-timers/src/modernFakeTimers.ts#L78
Replace `·this._clock.runToLastAsync()` with `⏎········this._clock.runToLastAsync(),⏎······`
|
Lint:
packages/jest-fake-timers/src/modernFakeTimers.ts#L120
Replace `·this._clock.tickAsync(msToRun)` with `⏎········this._clock.tickAsync(msToRun),⏎······`
|
|
Lint
Process completed with exit code 1.
|
collects coverage only from specified file:
e2e/__tests__/coverageReport.test.ts#L49
expect(received).toMatchSnapshot()
Snapshot name: `collects coverage only from specified file 1`
- Snapshot - 6
+ Received + 0
- ----------|---------|----------|---------|---------|-------------------
- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
- ----------|---------|----------|---------|---------|-------------------
- All files | 100 | 100 | 100 | 100 |
- file.js | 100 | 100 | 100 | 100 |
- ----------|---------|----------|---------|---------|-------------------
at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:49:18)
|
useRealTimers › restores timers to the native implementation:
e2e/__tests__/fakeTimers.test.ts#L66
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/fakeTimers.test.ts:66:29)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles circular inequality properly:
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 `Map`:
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)
|
Windows with shard 2/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
--findRelatedTests flag › generates coverage report for filename:
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:211:38)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
--findRelatedTests flag › generates coverage report for filename:
node:internal/child_process#L511
Could not find test summary in the output.
OUTPUT:
PASS __tests__/a.test.js
✓ a (4 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:211:38)
|
--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 (4 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)
|
Windows with shard 2/4 / Node v22.x
The operation was canceled.
|
macOS with shard 3/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
macOS with shard 3/3 / Node v22.x
The operation was canceled.
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
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)
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
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 4/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
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)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
Windows with shard 4/4 / Node v20.x
The operation was canceled.
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
The operation was canceled.
|
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 LTS using jest-jasmine2
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 v22.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|