chore(config): migrate renovate config #14452
Triggered via pull request
February 15, 2025 06:45
Status
Success
Total duration
17m 14s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
14s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
54s
TypeScript Compatibility
5m 37s
Typecheck Examples and Tests
3m 56s
Lint
1m 45s
Validate Yarn dependencies and constraints
13s
Node LTS on Ubuntu with leak detection
49s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
14 errors and 8 warnings
all passing › runs the tests in the correct order:
e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot()
Snapshot name: `all passing runs the tests in the correct order 1`
- Snapshot - 2
+ Received + 2
@@ -77,16 +77,16 @@
START "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "five"
+ END: "six"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "six"
+ END: "five"
at log (__tests__/concurrent.test.js:15:11)
console.log
END: "seven"
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
|
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)
|
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)
|
all passing › runs the tests in the correct order:
e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot()
Snapshot name: `all passing runs the tests in the correct order 1`
- Snapshot - 6
+ Received + 6
@@ -67,41 +67,41 @@
START "nine"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "nine"
+ END: "five"
at log (__tests__/concurrent.test.js:15:11)
console.log
START "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "five"
+ END: "six"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "six"
+ END: "seven"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "seven"
+ END: "nine"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "ten"
+ END: "eight"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "eight"
+ END: "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
afterAll
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
|
with skip › runs the tests in the correct order:
e2e/__tests__/circusConcurrent.test.ts#L47
expect(received).toMatchSnapshot()
Snapshot name: `with skip runs the tests in the correct order 1`
- Snapshot - 2
+ Received + 2
@@ -42,16 +42,16 @@
END: "two"
at log (__tests__/concurrent-skip.test.js:15:11)
console.log
- END: "seven"
+ END: "four"
at log (__tests__/concurrent-skip.test.js:15:11)
console.log
- END: "four"
+ END: "seven"
at log (__tests__/concurrent-skip.test.js:15:11)
console.log
END: "eight"
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:47:20)
|
processChild › handles circular inequality properly:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:56:35)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles circular inequality properly:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:56:35)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles `Map`:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:72:35)
|
processChild › handles `Map`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles `Map`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
Node LTS on Ubuntu with coverage (3/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 3/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 3/4 / Node v16.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Windows with shard 4/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 4/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 4/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|