Skip to content

Node Nightly CI

Node Nightly CI #221

Triggered via schedule April 19, 2024 12:04
Status Success
Total duration 11m 10s
Artifacts

nightly.yml

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

4 errors and 2 warnings
collects coverage only from specified file: e2e/__tests__/coverageReport.test.ts#L49
expect(received).toMatchSnapshot() Snapshot name: `collects coverage only from specified file 1` - Snapshot - 6 + Received + 0 - ----------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - ----------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - file.js | 100 | 100 | 100 | 100 | - ----------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:49:18)
useFakeTimers › allows clearing not faked timers: e2e/__tests__/fakeTimers.test.ts#L40
expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at Object.toBe (e2e/__tests__/fakeTimers.test.ts:40:29)
no babel-jest › fails with syntax error on flow types: e2e/__tests__/transform.test.ts#L89
expect(received).toMatch(expected) Expected pattern: /FAIL.*failsWithSyntaxError/ Received string: "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 process.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 process.processTimers (node:internal/timers:514:7) {· errno: -4048,· code: 'EPERM',· syscall: 'kill'· }··· Node.js v22.0.0-nightly2024041907f481cfcf" at Object.toMatch (e2e/__tests__/transform.test.ts:89:20)
no babel-jest › instrumentation with no babel-jest: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\transform-no-babel-jest' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/transform.test.ts:81:12)
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