Skip to content

Node Nightly CI

Node Nightly CI #60

Triggered via schedule June 9, 2024 12:24
Status Failure
Total duration 6h 1m 1s
Artifacts

nightly.yml

on: schedule
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
28s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
15s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
54s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
Matrix: test-macos / test-jasmine
Matrix: test-macos / test
Matrix: test-ubuntu / test-jasmine
Matrix: test-ubuntu / test
Matrix: test-windows / test-jasmine
Matrix: test-windows / test
Notify failed build
7s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 4 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)
updates the file size when a file changes: undefined#L1
kill EPERM at ChildProcessWorker.kill [as killChild] (packages/jest-worker/build/index.js:999:17)
updates the file size when a file changes: undefined#L1
kill EPERM at ChildProcessWorker.kill [as killChild] (packages/jest-worker/build/index.js:999:17)
Option showSeed › --showSeed changes report to output seed: node:internal/child_process#L512
Could not find test summary in the output. OUTPUT: node:events:498 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:512:26) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:512:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.0.0-nightly20240424ddd0a9e494 at extractSummary (e2e/Utils.ts:243:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
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: 1310737588 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:498 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:512:26) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:512:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.0.0-nightly20240424ddd0a9e494 at extractSummary (e2e/Utils.ts:243:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68
expect(received).toHaveLength(expected) Expected length: 2 Received length: 0 Received array: [] at Object.toHaveLength (e2e/__tests__/watchModePatterns.test.ts:68:19)
can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67
expect(received).toMatchSnapshot() Snapshot name: `can press "t" to filter by test name 1` - Snapshot - 25 + Received + 0 - <hideCursor> - <clearTerminal> - Pattern Mode Usage - › Press Esc to exit pattern mode. - › Press Enter to filter by a tests regex pattern. - - <showCursor> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › - <saveCursorPosition> - <moveCursorToRow6Column12> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › 2 - <saveCursorPosition> - <moveCursorToRow6Column13> - <restoreCursorPosition> - - <moveCursorDownBy1Row> - <eraseScreenDown> - at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:67:18)
test-macos / Node nightly on macos-latest (3/4)
The job running on runner GitHub Actions 2 has exceeded the maximum execution time of 360 minutes.
test-macos / Node nightly on macos-latest (3/4)
The operation was canceled.
Notify failed build
Issues are disabled for this repo
test-macos / Node Nightly on macos-latest using jest-jasmine2 (2/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
test-windows / Node Nightly on windows-latest using jest-jasmine2 (1/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
test-windows / Node nightly on windows-latest (1/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
test-windows / Node nightly on windows-latest (1/4)
Attempt 2 failed. Reason: Child_process exited with error code 1