Node Nightly CI #319
nightly.yml
on: schedule
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
24s
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
13s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
55s
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
2s
Annotations
7 errors and 5 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)
|
Option randomize › --randomize changes report to output seed:
node:internal/child_process#L512
Could not find test summary in the output.
OUTPUT:
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 process.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 process.processTimers (node:internal/timers:539:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v23.0.0-nightly20240726d955497874
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
|
--findRelatedTests flag › generates coverage report for filename:
node:internal/child_process#L512
Could not find test summary in the output.
OUTPUT:
PASS __tests__/a.test.js
✓ a (4 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-nightly20240726d955497874
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:211:38)
|
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)
|
can press "p" to filter by file name:
e2e/__tests__/watchModePatterns.test.ts#L51
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "p" to filter by file name: test results 1`
- Snapshot - 0
+ Received + 1
PASS __tests__/bar.spec.js
PASS __tests__/foo.spec.js
+ A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)
|
outputs coverage report:
e2e/__tests__/coverageReport.test.ts#L30
expect(received).toMatchSnapshot()
Snapshot name: `outputs coverage report 1`
- Snapshot - 15
+ Received + 0
- -------------------------------------|---------|----------|---------|---------|-------------------
- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
- -------------------------------------|---------|----------|---------|---------|-------------------
- All files | 60 | 0 | 50 | 60 |
- coverage-report | 47.36 | 0 | 25 | 50 |
- file.js | 100 | 100 | 100 | 100 |
- notRequiredInTestSuite.js | 0 | 0 | 0 | 0 | 8-19
- otherFile.js | 100 | 100 | 100 | 100 |
- sum.js | 87.5 | 100 | 50 | 100 |
- sumDependency.js | 0 | 0 | 0 | 0 | 8-13
- coverage-report/cached-duplicates/a | 100 | 100 | 100 | 100 |
- identical.js | 100 | 100 | 100 | 100 |
- coverage-report/cached-duplicates/b | 100 | 100 | 100 | 100 |
- identical.js | 100 | 100 | 100 | 100 |
- -------------------------------------|---------|----------|---------|---------|-------------------
at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:30:18)
|
test-windows / Node Nightly on windows-latest using jest-jasmine2 (1/4)
Final attempt failed. 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
|
test-windows / Node nightly on windows-latest (1/4)
Attempt 1 failed. Reason: 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
|