Skip to content

chore(deps): update dependency eslint-plugin-unicorn to v57 #14458

chore(deps): update dependency eslint-plugin-unicorn to v57

chore(deps): update dependency eslint-plugin-unicorn to v57 #14458

Triggered via pull request February 17, 2025 19:38
Status Failure
Total duration 16m 40s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
50s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
1m 19s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 32s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
3m 48s
TypeScript Compatibility
Typecheck Examples and Tests
3m 57s
Typecheck Examples and Tests
Lint
40s
Lint
Validate Yarn dependencies and constraints
23s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
49s
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

6 errors and 6 warnings
Lint
Process completed with exit code 2.
TypeScript Compatibility
Process completed with exit code 1.
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 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:51:18)
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)
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)
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)
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
Cache not found for keys: node-cache-Linux-x64-yarn-194c22c32f784e529d6b9755f398790f94ddf68dc42d82276ba90d20a461d033
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
Cache not found for keys: node-cache-macOS-arm64-yarn-194c22c32f784e529d6b9755f398790f94ddf68dc42d82276ba90d20a461d033
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
Cache not found for keys: node-cache-Windows-x64-yarn-194c22c32f784e529d6b9755f398790f94ddf68dc42d82276ba90d20a461d033
Windows with shard 1/4 / Node v23.x
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
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1