Skip to content

docs(CLI) Clarify functionality of --notify flag (taken from configuration docs) #14220

docs(CLI) Clarify functionality of --notify flag (taken from configuration docs)

docs(CLI) Clarify functionality of --notify flag (taken from configuration docs) #14220

Triggered via pull request November 7, 2024 13:48
Status Failure
Total duration 13m 55s
Artifacts

nodejs.yml

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

16 errors and 8 warnings
can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49
expect(received).toHaveLength(expected) Expected length: 2 Received length: 0 Received array: [] at Object.toHaveLength (e2e/__tests__/watchModePatterns.test.ts:49:19)
can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48
expect(received).toMatchSnapshot() Snapshot name: `can press "p" to filter by file name 1` - Snapshot - 39 + Received + 0 - <hideCursor> - <clearTerminal> - Pattern Mode Usage - › Press Esc to exit pattern mode. - › Press Enter to filter by a filenames regex pattern. - - <showCursor> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › - <saveCursorPosition> - <moveCursorToRow6Column12> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › b - <saveCursorPosition> - <moveCursorToRow6Column13> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › ba - <saveCursorPosition> - <moveCursorToRow6Column14> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › bar - <saveCursorPosition> - <moveCursorToRow6Column15> - <restoreCursorPosition> - - <moveCursorDownBy1Row> - <eraseScreenDown> - at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:48:18)
should call globalSetup function of multiple projects: node:internal/child_process#L511
Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: PASS project-1 project-1/setup1.test.js PASS project-2 project-2/setup2.test.js node:events:496 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:511:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.11.0 at json (e2e/runJest.ts:157:11) at Object.<anonymous> (e2e/__tests__/globalSetup.test.ts:98:29)
Option randomize › --randomize changes report to output seed: __tests__/get-seed.test.js#L9
Could not find test summary in the output. OUTPUT: FAIL __tests__/get-seed.test.js ● getSeed expect(received).toBe(expected) // Object.is equality Expected: 1234 Received: 502714718 7 | 8 | test('getSeed', () => { > 9 | expect(jest.getSeed()).toBe(1234); | ^ 10 | }); 11 | at Object.toBe (__tests__/get-seed.test.js:9:26) PASS __tests__/any-seed.test.js node:events:496 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:511:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.11.0 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
Option randomize › if randomize is present in the config the report will show the seed: node:internal/child_process#L511
Could not find test summary in the output. OUTPUT: node:events:496 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:511:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.11.0 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:42:37)
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 2` - 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:70:18)
collects coverage only from specified file: e2e/__tests__/coverageReport.test.ts#L49
expect(received).toMatchSnapshot() Snapshot name: `collects coverage only from specified file 1` - Snapshot - 6 + Received + 0 - ----------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - ----------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - file.js | 100 | 100 | 100 | 100 | - ----------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:49:18)
Windows with shard 1/4 / Node LTS using jest-jasmine2
Final attempt failed. Child_process exited with error 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)
processChild › handles functions: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles functions: 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 mixed structure: 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:111:35)
skips: e2e/__tests__/globals.test.ts#L119
expect(received).toMatchSnapshot() Snapshot name: `skips 1` - Snapshot - 1 + Received + 25 @@ -8,6 +8,30 @@ ○ skipped it ○ skipped test describe.skip ○ skipped test describe - ○ skipped test" + ○ skipped 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:119:16)
babel-jest-async › should use babel-jest's async transforms: node:internal/child_process#L511
Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: node:events:496 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) 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) [... lines matching original stack trace ...] at processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.11.0 at json (e2e/runJest.ts:157:11) at Object.<anonymous> (e2e/__tests__/transform.test.ts:313:39)
--findRelatedTests flag › coverage configuration is applied correctly: node:internal/child_process#L511
Could not find test summary in the output. OUTPUT: PASS __tests__/a.test.js ✓ a (5 ms) node:events:496 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) 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) [... lines matching original stack trace ...] at processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.11.0 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:244:43)
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 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 2 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 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
Windows with shard 2/4 / Node LTS using jest-jasmine2
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