Node Nightly CI #341
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
15s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
44s
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
5 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)
|
babel-plugin-jest-hoist › 10. TS typeof usage in jest.mock:
undefined#L1
AtomicsWaitError: Unexpected error
at _Lock.lock (node_modules/make-synchronized/index.cjs:132:11)
|
useFakeTimers › enables fake timers from Jest object:
e2e/__tests__/fakeTimers.test.ts#L20
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/fakeTimers.test.ts:20:29)
|
can press "u" to update snapshots:
e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "u" to update snapshots: test results 1`
- Snapshot - 0
+ Received + 1
@@ -14,7 +14,8 @@
| ^
at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35)
› 1 snapshot failed.
+ 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.
Snapshot Summary
› 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them."
at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
|
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: -1868113710
7 |
8 | test('getSeed', () => {
> 9 | expect(jest.getSeed()).toBe(1234);
| ^
10 | });
11 |
at Object.toBe (__tests__/get-seed.test.js:9:26)
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:614:17)
at process.processTimers (node:internal/timers:549: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:549:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v23.0.0-nightly202408168d37584874
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
|
test-macos / Node Nightly on macos-latest using jest-jasmine2 (2/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
test-ubuntu / Node Nightly on ubuntu-latest using jest-jasmine2 (4/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 using jest-jasmine2 (1/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|