You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
memory consumption ramps from 7GB to 32GB while running npm run test which is not quite ideal
im running this on my personal machine. cannot run all tests in a single batch, will need to run tests in multiple batches if this problem is persistant
if this is intended, this is still not ideal as most of the situations people will have less than 32G memory from their dev machines. would could consider modify the scripts to let jest run tests in multiple batches
if this is not an intendend behavior, could indicate a memory leak when setting up test suites or problem within Jest.
system setting
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
The text was updated successfully, but these errors were encountered:
jzhao62
changed the title
Potential Memory Leak while frontend unit testcases
Potential Memory Leak while running frontend unit testcases locally
Apr 6, 2024
jzhao62
changed the title
Potential Memory Leak while running frontend unit testcases locally
Huge memory consumption while running frontend unit testcases locally
Apr 6, 2024
jzhao62
changed the title
Huge memory consumption while running frontend unit testcases locally
huge memory consumption while running frontend unit testcases locally
Apr 6, 2024
Bug description
How to reproduce the bug
cd superset-frontend
npm run test
as indicated in the docScreenshots/recordings
sample-snapshot-2024-04-05_23.35.40.mp4
Superset version
master / latest-dev
Python version
3.10
Node version
18 or greater
Browser
Chrome
Additional context
Checklist
The text was updated successfully, but these errors were encountered: