Skip to content

Node Nightly CI

Node Nightly CI #316

Triggered via schedule July 23, 2024 12:04
Status Failure
Total duration 6h 0m 49s
Artifacts

nightly.yml

on: schedule
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
12s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
48s
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
5s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 5 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)
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)
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)
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)
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)
processChild › handles functions: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles functions: e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test '\\?\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)
all 3 test files should complete: 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:601:17) at process.processTimers (node:internal/timers:539: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:539:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v23.0.0-nightly20240723cad73dadba at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/workerRestartBeforeSend.test.ts:13:35)
Node crawler does not pick up symlinked files by default: e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
test-windows / Node nightly on windows-latest (3/4)
unable to access 'https://github.com/jestjs/jest/': OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
test-macos / Node Nightly on macos-latest using jest-jasmine2 (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 using jest-jasmine2 (3/4)
The operation was canceled.
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 using jest-jasmine2 (1/4)
Attempt 2 failed. Reason: Child_process exited with error code 1
test-windows / Node Nightly on windows-latest using jest-jasmine2 (4/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
test-windows / Node Nightly on windows-latest using jest-jasmine2 (4/4)
Attempt 2 failed. Reason: Child_process exited with error code 1