Skip to content

feat(jest-fake-timers): Add feature to enable automatically advancing… #14112

feat(jest-fake-timers): Add feature to enable automatically advancing…

feat(jest-fake-timers): Add feature to enable automatically advancing… #14112

Triggered via pull request September 20, 2024 23:32
Status Cancelled
Total duration 14m 7s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
18s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
48s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 32s
TypeScript Compatibility
Typecheck Examples and Tests
3m 47s
Typecheck Examples and Tests
Lint
1m 35s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 5s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

31 errors and 6 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)
works with single typescript config that imports something: e2e/__tests__/typescriptConfigFile.test.ts#L38
expect(received).toContain(expected) // indexOf Expected substring: "PASS __tests__/mytest.alpha.js" Received string: "Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at ChildProcessWorker.killChild (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1000:17) at ChildProcessWorker.forceExit (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1005:33) at Timeout._onTimeout (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:567:16) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' }" at Object.toContain (e2e/__tests__/typescriptConfigFile.test.ts:38:18)
works with single typescript config that imports something: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\typescript-config-file' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/typescriptConfigFile.test.ts:16:24)
works with multiple typescript configs: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\typescript-config-file' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/typescriptConfigFile.test.ts:15:25)
works with multiple typescript configs: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\typescript-config-file' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/typescriptConfigFile.test.ts:16:24)
works with multiple typescript configs that import something: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\typescript-config-file' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/typescriptConfigFile.test.ts:15:25)
works with multiple typescript configs that import something: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\typescript-config-file' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/typescriptConfigFile.test.ts:16:24)
works with single typescript config that does not import anything with project's moduleResolution set to Node16: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\typescript-config-file' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/typescriptConfigFile.test.ts:15:25)
works with single typescript config that does not import anything with project's moduleResolution set to Node16: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\typescript-config-file' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/typescriptConfigFile.test.ts:16:24)
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)
Windows with shard 4/4 / Node v16.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
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.
Windows with shard 4/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-autoAdvance' exists
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)
processChild › handles `Symbol`: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles `Symbol`: 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: 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:98:35)
Windows with shard 4/4 / Node LTS using jest-jasmine2
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 3/4 / Node v22.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 4/4 / Node v16.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 LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1