Skip to content

Node Nightly CI

Node Nightly CI #265

Triggered via schedule June 2, 2024 12:03
Status Success
Total duration 9m 9s
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
0s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
collects coverage from duplicate files avoiding shared cache: e2e/__tests__/coverageReport.test.ts#L179
expect(received).toMatchSnapshot() Snapshot name: `collects coverage from duplicate files avoiding shared cache 1` - Snapshot - 9 + Received + 0 - ---------------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - ---------------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - a | 100 | 100 | 100 | 100 | - identical.js | 100 | 100 | 100 | 100 | - b | 100 | 100 | 100 | 100 | - identical.js | 100 | 100 | 100 | 100 | - ---------------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:179:18)
supports json preset: e2e/__tests__/presets.test.ts#L12
expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at Object.toBe (e2e/__tests__/presets.test.ts:12:27)
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-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-macos / Node Nightly on macos-latest using jest-jasmine2 (2/4)
Attempt 1 failed. Reason: Child_process exited with error code 1