Skip to content

Node Nightly CI

Node Nightly CI #173

Triggered via schedule March 2, 2024 12:03
Status Failure
Total duration 9m 54s
Artifacts

nightly.yml

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

6 errors and 5 warnings
--findRelatedTests flag › coverage configuration is applied correctly: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
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)
Option randomize › --randomize changes report to output seed: __tests__/get-seed.test.js#L9
Could not find test summary in the output. OUTPUT: PASS __tests__/any-seed.test.js FAIL __tests__/get-seed.test.js ● getSeed expect(received).toBe(expected) // Object.is equality Expected: 1234 Received: 1185122675 7 | 8 | test('getSeed', () => { > 9 | expect(jest.getSeed()).toBe(1234); | ^ 10 | }); 11 | at Object.toBe (__tests__/get-seed.test.js:9:26) node:events:497 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 v22.0.0-nightly2024030214293814a7 at extractSummary (e2e/Utils.ts:243:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
should call globalSetup function of multiple projects: node:internal/child_process#L512
Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: PASS project-2 project-2/setup.test.js PASS project-1 project-1/setup.test.js node:events:497 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 v22.0.0-nightly2024030214293814a7 at json (e2e/runJest.ts:155:11) at Object.<anonymous> (e2e/__tests__/globalSetup.test.ts:98:29)
test-windows / Node Nightly on windows-latest using jest-jasmine2 (1/4)
Final attempt failed. Child_process exited with error code 1
test-windows / Node nightly on windows-latest (3/4)
Final attempt failed. 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
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 (1/4)
Attempt 2 failed. Reason: Child_process exited with error code 1
test-windows / Node nightly on windows-latest (3/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
test-windows / Node nightly on windows-latest (3/4)
Attempt 2 failed. Reason: Child_process exited with error code 1