Closed trivikr closed 1 year ago
Latest commit: 9c9870f8afb4006d78c073fd442b82a48bed11f6
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The process exits with just 46MB of heap size
https://github.com/trivikr/vitest-codemod/actions/runs/4195888311/jobs/7276077638
➤ YN0000: [@vitest-codemod/jest]: Process started
➤ YN0000: [@vitest-codemod/jest]: PASS src/__fixtures__/expect/toHaveProperty.input.js (34 MB heap size)
➤ YN0000: [@vitest-codemod/jest]: PASS src/__fixtures__/returns/results.input.js (44 MB heap size)
➤ YN0000: [@vitest-codemod/jest]: PASS src/__fixtures__/mock/mockReset.input.js (42 MB heap size)
➤ YN0000: [@vitest-codemod/jest]: PASS src/__fixtures__/mock/spyOn.input.js (40 MB heap size)
➤ YN0000: [@vitest-codemod/jest]: PASS src/__fixtures__/async/promises.input.js (48 MB heap size)
➤ YN0000: [@vitest-codemod/jest]: PASS src/__fixtures__/snapshot/addSnapshotSerializer.input.js (46 MB heap size)
➤ YN0000: [@vitest-codemod/jest]: Process exited (exit code 1), completed in 7s 587ms
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Issue
Refs: https://github.com/trivikr/vitest-codemod/issues/129
Description
Log heap usage in jest tests to check where it's going out of memory.
Testing
CI