Release command log items in run mode

[mschile]

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

[hegeds]

Hey,
just curious what are the plans for this? I'm just wondering, because from my perspective it would be great, if the number of retained commands would be user configurable 🤔

[mschile]

Hi @hegeds 👋, my plan is to remove the logs from the reporter for any successful tests in run mode. In this context, I'm not sure there will be a lot of benefit to have the number of retained commands to be user configurable. That may be something to consider for open mode though.

[hegeds]

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

[mschile]

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.

[cypress-bot]

Released in 12.5.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v12.5.0, please open a new issue.