chore(deps): replace dependency eslint-plugin-eslint-comments with @eslint-community/eslint-plugin-eslint-comments ^3.2.0 #14230
SimenBnodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
53s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
58s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 44s
TypeScript Compatibility
5m 22s
Typecheck Examples and Tests
3m 53s
Lint
1m 49s
Validate Yarn dependencies and constraints
19s
Node LTS on Ubuntu with leak detection
52s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
16 errors and 40 warnings
|
should not transpile the transformer:
e2e/__tests__/globalSetup.test.ts#L168
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/globalSetup.test.ts:168:20)
|
|
outputs coverage report as json:
e2e/__tests__/coverageReport.test.ts#L102
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/coverageReport.test.ts:102:20)
|
|
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)
|
|
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 1`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.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.
+
PASS __tests__/foo.spec.js
at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)
|
|
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)
|
|
outputs coverage report as json:
e2e/__tests__/coverageReport.test.ts#L102
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/coverageReport.test.ts:102:20)
|
|
globalSetup works with ESM modules:
e2e/__tests__/globalSetup.test.ts#L202
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/globalSetup.test.ts:202:20)
|
|
can press "t" to filter by test name:
e2e/__tests__/watchModePatterns.test.ts#L70
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "t" to filter by test name: test results 1`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.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.
+
PASS __tests__/foo.spec.js
at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70:18)
|
|
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)
|
|
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)
|
|
only with expand arg:
e2e/__tests__/globals.test.ts#L244
expect(received).toMatchSnapshot()
Snapshot name: `only with expand arg 1`
- Snapshot - 1
+ Received + 25
@@ -7,6 +7,30 @@
✓ it
✓ test
describe.only
✓ test
describe
- ✓ test"
+ ✓ test
+
+
+ node:events:496
+ throw er; // Unhandled 'error' event
+ ^
+
+ 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)
+ Emitted 'error' event on ChildProcess instance at:
+ at ChildProcess.kill (node:internal/child_process:511:12)
+ at ChildProcessWorker.killChild (D:\a\jest\jest\packages\jest-worker\build\index.js:1000:17)
+ [... lines matching original stack trace ...]
+ at processTimers (node:internal/timers:529:7) {
+ errno: -4048,
+ code: 'EPERM',
+ syscall: 'kill'
+ }
+
+ Node.js v22.11.0"
at Object.toMatchSnapshot (e2e/__tests__/globals.test.ts:244:16)
|
|
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
|
|
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 leak detection
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
|
|
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 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 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
|
|
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
|
|
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
|
|
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 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 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 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
|
|
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
|
|
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 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 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 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
|
|
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
|
|
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 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 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 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 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 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 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 v16.x
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
|
|
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
|
|
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
|
|
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 v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node v20.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node v22.x
Attempt 2 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 LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Attempt 2 failed. Reason: Child_process exited with error code 1
|