Skip to content

Mitigate memory leaks in jest-environment-node #13982

Mitigate memory leaks in jest-environment-node

Mitigate memory leaks in jest-environment-node #13982

Triggered via pull request August 2, 2024 11:38
Status Cancelled
Total duration 20m 28s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
17s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
28s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
56s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 45s
TypeScript Compatibility
Typecheck Examples and Tests
3m 57s
Typecheck Examples and Tests
Lint
1m 47s
Lint
Validate Yarn dependencies and constraints
18s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 7s
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

12 errors and 5 warnings
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
--findRelatedTests flag › coverage configuration is applied correctly: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
gets changed files for hg: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
gets changed files for hg: e2e/__tests__/jestChangedFiles.test.ts#L394
expect(received).toEqual(expected) // deep equality - Expected - 0 + Received + 36 Array [ + ".watchmanconfig", + "00changelog.i", + "266d5165b1f04745f6b4df89a1712a053f5ea6", + "26dfeeb6e641a33dae4961196235bdb965b21b", + "3c8d3af3016988d8abb98e6a35854f088e8704", + "6d6c73d3d5a72254e74f72e6725d1402c9ddc8", + "9de29bb2d1d6434b8b29ae775ad8c2e48c5391", + "COMMIT_EDITMSG", + "HEAD", + "HEAD", + "ab0f70703a36d51ba9ab4ac3db92ede266f2d4", + "applypatch-msg.sample", + "b83fd321d87232fd6688dd32631f7c27cd36cb", + "commit-msg.sample", + "config", + "description", + "exclude", + "file1.js", + "file1.test.js", "file1.txt", "file2.txt", "file3.txt", + "fsmonitor-watchman.sample", + "index", + "main", + "main", + "package.json", + "post-update.sample", + "pre-applypatch.sample", + "pre-commit.sample", + "pre-merge-commit.sample", + "pre-push.sample", + "pre-rebase.sample", + "pre-receive.sample", + "prepare-commit-msg.sample", + "push-to-checkout.sample", + "requires", + "sendemail-validate.sample", + "update.sample", ] at Object.toEqual (e2e/__tests__/jestChangedFiles.test.ts:394:70)
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 circular inequality properly: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles circular inequality properly: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
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:56:35)
macOS with shard 1/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-fix-memory-leak' exists
macOS with shard 1/3 / Node v22.x
The operation was canceled.
Windows with shard 2/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node LTS using jest-jasmine2
Attempt 2 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 LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1