Node Nightly CI #300
SimenBnightly.yml
on: schedule
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
18s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
48s
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
6 errors and 4 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)
|
|
runs tests in only test.js and spec.js:
node:internal/child_process#L512
Can't parse JSON.
ERROR: SyntaxError Unexpected end of JSON input
STDOUT:
STDERR: 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-nightly202407028f71a1b248
at json (e2e/runJest.ts:157:11)
at Object.<anonymous> (e2e/__tests__/testInRoot.test.ts:12:37)
|
|
--findRelatedTests flag › coverage configuration is applied correctly:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
|
|
Node crawler does not pick up symlinked files by default:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
|
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
|
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 (2/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
test-windows / Node nightly on windows-latest (2/4)
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
test-windows / Node nightly on windows-latest (4/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|