-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release command log items in run mode #25230
Comments
Hey, |
Hi @hegeds 👋, my plan is to remove the logs from the reporter for any successful tests in |
oh I see, this can be a major improvement in suites where there are multiple quick test cases! However we also have quite a few longer test cases, where we have OOM crashes. This is why I would be interested in a solution, where one could set that only the last x number of logs are kept even in headless mode |
Thanks for the clarification @hegeds. We are hopefully releasing this change today. If you are still receiving OOM crashes after updating, could you please log a new memory issue. We have discussed single tests that consume large amounts of memory but we would like some more metrics before we make any changes. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
What would you like?
In headless run mode, the command log cannot be interacted with, as such, the logs in the command log do not need to be retained and can be released. See this comment for additional details.
Why is this needed?
Don't unnecessarily consume memory.
Other
No response
The text was updated successfully, but these errors were encountered: