Skip to content

Node Nightly CI

Node Nightly CI #235

Triggered via schedule May 3, 2024 12:04
Status Failure
Total duration 15m 5s
Artifacts

nightly.yml

on: schedule
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
22s
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
37s
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

7 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)
test-macos / Node nightly on macos-latest (1/4)
Unexpected HTTP response: 500
test-macos / Node nightly on macos-latest (3/4)
Unexpected HTTP response: 500
test-macos / Node nightly on macos-latest (4/4)
Unexpected HTTP response: 500
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)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
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: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-nightly2024050315456e4e57" at Object.toMatchSnapshot (e2e/__tests__/globals.test.ts:244:16)
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 (2/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 1 failed. Reason: Child_process exited with error code 1