Node Nightly CI #297
nightly.yml
on: schedule
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
19s
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
22s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 18s
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
Annotations
3 errors and 3 warnings
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)
|
--findRelatedTests flag › coverage configuration is applied correctly:
node:internal/child_process#L512
Could not find test summary in the output.
OUTPUT:
PASS __tests__/a.test.js
✓ a (3 ms)
node:events:498
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:512:26)
at listOnTimeout (node:internal/timers:601:17)
at processTimers (node:internal/timers:539:7)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess.kill (node:internal/child_process:512:12)
[... lines matching original stack trace ...]
at processTimers (node:internal/timers:539:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v23.0.0-nightly202407028f71a1b248
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:244:43)
|
resolves projects and their <rootDir> properly:
e2e/__tests__/multiProjectRunner.test.ts#L373
expect(received).toMatch(expected)
Expected substring: "Ran all test suites in 2 projects."
Received string: "PASS project1/__tests__/test.test.js
PASS project2/__tests__/test.test.js
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:601:17)·
at process.processTimers (node:internal/timers:539: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:539:7) {·
errno: -4048,·
code: 'EPERM',·
syscall: 'kill'·
}···
Node.js v23.0.0-nightly202407028f71a1b248"
at Object.toMatch (e2e/__tests__/multiProjectRunner.test.ts:373:18)
|
test-macos / Node Nightly on macos-latest using jest-jasmine2 (2/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-windows / Node Nightly on windows-latest using jest-jasmine2 (3/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|