chore: update ESLint to v9 #14485
fiskernodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
13s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
21s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
54s
TypeScript Compatibility
5m 32s
Typecheck Examples and Tests
3m 54s
Lint
1m 51s
Validate Yarn dependencies and constraints
15s
Node LTS on Ubuntu with leak detection
44s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
81 errors and 16 warnings
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Node LTS on Ubuntu with coverage (4/4)
Final attempt failed. Child_process exited with error code 1
|
|
TypeScript Compatibility
Process completed with exit code 1.
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
Final attempt failed. Child_process exited with error code 1
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Ubuntu with shard 4/4 / Node v23.x
Final attempt failed. Child_process exited with error code 1
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Ubuntu with shard 4/4 / Node v20.x
Final attempt failed. Child_process exited with error code 1
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Ubuntu with shard 4/4 / Node v18.x
Final attempt failed. Child_process exited with error code 1
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Ubuntu with shard 4/4 / Node v16.x
Final attempt failed. Child_process exited with error code 1
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Ubuntu with shard 4/4 / Node v22.x
Final attempt failed. Child_process exited with error code 1
|
|
macOS with shard 3/3 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
macOS with shard 3/3 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
macOS with shard 3/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
macOS with shard 3/3 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 4/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 4/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 2/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-eslint9' 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-eslint9' exists
|
|
Windows with shard 3/4 / Node v20.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
macOS with shard 2/3 / Node v22.x
The operation was canceled.
|
|
Windows with shard 2/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 2/4 / Node v23.x
The operation was canceled.
|
|
Windows with shard 4/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 4/4 / Node v18.x
The operation was canceled.
|
|
Windows with shard 2/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
--findRelatedTests flag › coverage configuration is applied correctly:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
|
|
Windows with shard 2/4 / Node v18.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 3/4 / Node v23.x
The operation was canceled.
|
|
Windows with shard 2/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 2/4 / Node v16.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
macOS with shard 2/3 / Node v23.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-eslint9' exists
|
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-eslint9' 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 3/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 3/4 / Node v18.x
The operation was canceled.
|
|
Windows with shard 2/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 2/4 / Node v22.x
The operation was canceled.
|
|
macOS with shard 3/3 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
macOS with shard 3/3 / Node v16.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 3/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-eslint9' exists
|
|
Windows with shard 4/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-eslint9' exists
|
|
when out of memory occurs the worker is killed and exits:
undefined#L1
expect(jest.fn()).toHaveBeenCalledWith(...expected)
Expected: [Error: Jest worker ran out of memory and crashed], null
Received: [Error: A jest worker process (pid=undefined) was terminated by another process: signal=SIGABRT, exitCode=null. Operating system logs may contain more information on why this occurred.], null
Number of calls: 1
at Object.toHaveBeenCalledWith (packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:476:24)
|
|
Windows with shard 4/4 / Node v16.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
with skip › runs the tests in the correct order:
e2e/__tests__/circusConcurrent.test.ts#L47
expect(received).toMatchSnapshot()
Snapshot name: `with skip runs the tests in the correct order 1`
- Snapshot - 3
+ Received + 3
@@ -47,21 +47,21 @@
END: "seven"
at log (__tests__/concurrent-skip.test.js:15:11)
console.log
- END: "four"
+ END: "ten"
at log (__tests__/concurrent-skip.test.js:15:11)
console.log
- END: "eight"
+ END: "four"
at log (__tests__/concurrent-skip.test.js:15:11)
console.log
- END: "ten"
+ END: "eight"
at log (__tests__/concurrent-skip.test.js:15:11)
console.log
afterAll
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:47:20)
|
|
macOS with shard 2/3 / Node v16.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-eslint9' exists
|
|
Windows with shard 3/4 / Node v16.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-eslint9' exists
|
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
The operation was canceled.
|
|
Node LTS on Ubuntu with coverage (4/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Node LTS on Ubuntu with coverage (4/4)
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v20.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v18.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v16.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v22.x
Attempt 2 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
|
|
macOS with shard 2/3 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|