Skip to content

Node Nightly CI

Node Nightly CI #172

Triggered via schedule March 1, 2024 12:04
Status Failure
Total duration 17m 42s
Artifacts

nightly.yml

on: schedule
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
45s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
29s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
37s
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
4s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
default reporter › prints failure messages when total number of test suites is over summaryThreshold: e2e/__tests__/summaryThreshold.test.ts#L21
expect(received).toMatch(expected) Expected pattern: /Summary of all failing tests(\n|.)*expect\(1\)\.toBe\(0\)/ Received string: "node:events:497· 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-nightly2024030130c9181994" at Object.toMatch (e2e/__tests__/summaryThreshold.test.ts:21:22)
Option showSeed › --showSeed 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: 56045057 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-nightly2024030130c9181994 at extractSummary (e2e/Utils.ts:243:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
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 (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