Skip to content

Node Nightly CI

Node Nightly CI #200

Triggered via schedule March 29, 2024 12:03
Status Success
Total duration 10m 31s
Artifacts

nightly.yml

on: schedule
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
30s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
13s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
47s
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
0s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L51
expect(received).toMatchSnapshot(hint) Snapshot name: `can press "p" to filter by file name: test results 2` - Snapshot - 0 + Received + 2 PASS __tests__/bar.spec.js ✓ bar 1 ✓ bar 2 + + 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:51:18)
test-ubuntu / Node Nightly on ubuntu-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-macos / Node Nightly on macos-latest using jest-jasmine2 (4/4)
Attempt 1 failed. Reason: Child_process exited with error code 1