Skip to content

fix(deps): update dependency react-markdown to v10 (#15518) #14465

fix(deps): update dependency react-markdown to v10 (#15518)

fix(deps): update dependency react-markdown to v10 (#15518) #14465

Triggered via push February 21, 2025 06:56
Status Success
Total duration 18m 3s
Artifacts

nodejs.yml

on: push
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
47s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
58s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
2m 8s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 39s
TypeScript Compatibility
Typecheck Examples and Tests
4m 4s
Typecheck Examples and Tests
Lint
1m 53s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
45s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 8 warnings
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 - 2 + Received + 2 @@ -27,21 +27,21 @@ START "five" at log (__tests__/concurrent.test.js:15:11) console.log - END: "three" + END: "one" at log (__tests__/concurrent.test.js:15:11) console.log START "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "one" + END: "three" at log (__tests__/concurrent.test.js:15:11) console.log START "seven" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
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 @@ -87,16 +87,16 @@ END: "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log END: "eight" 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)
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 - 5 + Received + 5 @@ -67,36 +67,36 @@ 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: "nine" at log (__tests__/concurrent.test.js:15:11) console.log - END: "six" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log END: "eight" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
Cache not found for keys: node-cache-Linux-x64-yarn-1ef2203c43dede1e48a5e55334e01e70aa166836f3e89002bce4d69c81add8a0
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
Cache not found for keys: node-cache-macOS-arm64-yarn-1ef2203c43dede1e48a5e55334e01e70aa166836f3e89002bce4d69c81add8a0
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
Cache not found for keys: node-cache-Windows-x64-yarn-1ef2203c43dede1e48a5e55334e01e70aa166836f3e89002bce4d69c81add8a0
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
macOS with shard 2/3 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
macOS with shard 2/3 / Node v23.x
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 3/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1