Skip to content

Draft: --logHeapUsage: also log process id #12943

Draft: --logHeapUsage: also log process id

Draft: --logHeapUsage: also log process id #12943

Triggered via pull request November 16, 2023 14:05
Status Failure
Total duration 41m 54s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
16s
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
37s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
4m 26s
TypeScript Compatibility
Typecheck Examples and Tests
2m 55s
Typecheck Examples and Tests
Lint
1m 39s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
2m 14s
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
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)
Windows with shard 1/4 / Node v21.x
Process completed with exit code 1.
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)
handles functions that close over outside variables: e2e/__tests__/complexItemsInErrors.ts#L61
expect(received).toMatchSnapshot() Snapshot name: `handles functions that close over outside variables 1` - Snapshot - 0 + Received + 2 @@ -11,10 +11,12 @@ 6 | error.someProp = () => someString; 7 | at Object.<anonymous> (__tests__/test-1.js:4:17) + 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. + FAIL __tests__/test-2.js ● dummy boom ↵ at Object.toMatchSnapshot (e2e/__tests__/complexItemsInErrors.ts:61:16)
macOS with shard 2/3 / Node LTS using jest-jasmine2
Process completed with exit code 1.