Skip to content

docs: Remove repeated text in Update GlobalAPI.md #14469

docs: Remove repeated text in Update GlobalAPI.md

docs: Remove repeated text in Update GlobalAPI.md #14469

Triggered via pull request February 21, 2025 19:33
Status Success
Total duration 16m 23s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
18s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
20s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
36s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 36s
TypeScript Compatibility
Typecheck Examples and Tests
4m 6s
Typecheck Examples and Tests
Lint
1m 54s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
55s
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

6 errors and 6 warnings
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 - 3 + Received + 3 @@ -47,21 +47,21 @@ END: "seven" at log (__tests__/concurrent-skip.test.js:15:11) console.log - END: "four" + END: "ten" at log (__tests__/concurrent-skip.test.js:15:11) console.log - END: "eight" + END: "four" at log (__tests__/concurrent-skip.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent-skip.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:47: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 @@ -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)
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)
processChild › handles `Map`: e2e/__tests__/nonSerializableStructuresInequality.test.ts#L80
expect(received).toMatchSnapshot() Snapshot name: `processChild handles \`Map\` 1` - Snapshot - 1 + Received + 3 @@ -34,6 +34,8 @@ 1 | it('test', () => { > 2 | expect(new Map([[1, "2"]])).toEqual(new Map([[1, "3"]])); | ^ 3 | }); - at Object.toEqual (__tests__/test-2.js:2:31)" + at Object.toEqual (__tests__/test-2.js:2:31) + + 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__/nonSerializableStructuresInequality.test.ts:80:18)
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)
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 2` - Snapshot - 0 + Received + 1 PASS __tests__/bar.spec.js ✓ bar › 1 snapshot updated. + 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 updated from 1 test suite. at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
Windows with shard 3/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
macOS with shard 2/3 / Node v22.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 4/4 / Node v20.x
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 1/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1