Skip to content

Node Nightly CI

Node Nightly CI #261

Triggered via schedule May 29, 2024 12:04
Status Failure
Total duration 6h 0m 51s
Artifacts

nightly.yml

on: schedule
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
19s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
14s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
38s
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
3s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 5 warnings
cannot test with no implementation with expand arg: e2e/__tests__/globals.test.ts#L261
expect(received).toMatchSnapshot() Snapshot name: `cannot test with no implementation with expand arg 1` - Snapshot - 1 + Received + 25 @@ -6,6 +6,30 @@ 1 | it('it', () => {}); > 2 | it('it, no implementation'); | ^ 3 | test('test, no implementation'); - at Object.it (__tests__/onlyConstructs.test.js:2:1)" + at Object.it (__tests__/onlyConstructs.test.js:2:1) + + + node:events:498 + throw er; // Unhandled 'error' event + ^ + + Error: kill EPERM + at ChildProcess.kill (node:internal/child_process:512:26) + at ChildProcessWorker.killChild (D:\a\jest\jest\packages\jest-worker\build\index.js:999:17) + at ChildProcessWorker.forceExit (D:\a\jest\jest\packages\jest-worker\build\index.js:1004:33) + at Timeout._onTimeout (D:\a\jest\jest\packages\jest-worker\build\index.js:567:16) + at listOnTimeout (node:internal/timers:573:17) + at processTimers (node:internal/timers:514:7) + Emitted 'error' event on ChildProcess instance at: + at ChildProcess.kill (node:internal/child_process:512:12) + at ChildProcessWorker.killChild (D:\a\jest\jest\packages\jest-worker\build\index.js:999:17) + [... lines matching original stack trace ...] + at processTimers (node:internal/timers:514:7) { + errno: -4048, + code: 'EPERM', + syscall: 'kill' + } + + Node.js v23.0.0-nightly20240529c0c598d753" at Object.toMatchSnapshot (e2e/__tests__/globals.test.ts:261:31)
globalSetup is triggered once before all test suites: node:internal/child_process#L512
Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: PASS __tests__/setup2.test.js PASS __tests__/setup3.test.js PASS __tests__/setup1.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 v23.0.0-nightly20240529c0c598d753 at json (e2e/runJest.ts:157:11) at Object.<anonymous> (e2e/__tests__/globalSetup.test.ts:57:29)
Snapshot › Validation › works on subsequent runs without `-u`: node:internal/child_process#L512
Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: PASS __tests__/snapshot.test_copy.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 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 processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v23.0.0-nightly20240529c0c598d753 at json (e2e/runJest.ts:157:11) at Object.<anonymous> (e2e/__tests__/snapshot.test.ts:243:36)
Node crawler does not pick up symlinked files by default: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '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
EBUSY: resource busy or locked, rmdir '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)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '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)
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)
--findRelatedTests flag › generates coverage report for filename: node:internal/child_process#L512
Could not find test summary in the output. OUTPUT: PASS __tests__/a.test.js ✓ a (6 ms) 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 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 processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v23.0.0-nightly20240529c0c598d753 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:211:38)
test-macos / Node Nightly on macos-latest using jest-jasmine2 (3/4)
The job running on runner GitHub Actions 3 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 (2/4)
The job running on runner GitHub Actions 5 has exceeded the maximum execution time of 360 minutes.
test-macos / Node nightly on macos-latest (2/4)
The operation was canceled.
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 (1/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
test-windows / Node nightly on windows-latest (4/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
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 (2/4)
Attempt 1 failed. Reason: Child_process exited with error code 1