Skip to content

fix: update @sinonjs/fake-timers #14385

fix: update @sinonjs/fake-timers

fix: update @sinonjs/fake-timers #14385

Triggered via pull request January 20, 2025 10:48
Status Failure
Total duration 28m 8s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
17s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
16s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
47s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 52s
TypeScript Compatibility
Typecheck Examples and Tests
4m 7s
Typecheck Examples and Tests
Lint
1m 54s
Lint
Validate Yarn dependencies and constraints
21s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
46s
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

7 errors and 39 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 "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)
Custom Reporters Integration › supports reporter written in ESM: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\custom-reporters-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/customReporters.test.ts:16:24)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -92,16 +92,16 @@ END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent.test.js:15:11) console.log - END: "eight" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 3 + Received + 3 @@ -82,21 +82,21 @@ END: "five" at log (__tests__/concurrent.test.js:15:11) console.log - END: "six" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log END: "eight" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -67,21 +67,21 @@ START "nine" at log (__tests__/concurrent.test.js:15:11) console.log - END: "nine" + END: "five" at log (__tests__/concurrent.test.js:15:11) console.log START "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "five" + END: "nine" at log (__tests__/concurrent.test.js:15:11) console.log END: "six" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
Windows with shard 3/4 / Node v20.x
Final attempt failed. Child_process exited with error code 1
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with leak detection
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Validate Yarn dependencies and constraints
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (1/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
TypeScript Compatibility
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Typecheck Examples and Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (2/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (4/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (3/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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 LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v20.x
Attempt 2 failed. Reason: Child_process exited with error code 1