Skip to content
Node Nightly CI

Node Nightly CI #1

Sign in to view logs

Node Nightly CI

Node Nightly CI #1

Triggered via schedule September 29, 2023 12:31
@ziyad-elabid-nwziyad-elabid-nw
⁠ 7f1d897
main
Status Failure
Total duration 16m 8s
Artifacts –

nightly.yml

on: schedule
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
51s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
33s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 13s
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

4 errors
handles functions that close over outside variables: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
handles functions that close over outside variables: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\complex-errors' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/complexItemsInErrors.ts:28:10)
test-windows / Node Nightly on windows-latest using jest-jasmine2 (2/4)
Process completed with exit code 1.
Notify failed build
Resource not accessible by integration