-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Better message for memory limit errors #3613
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
Comments
We have some code written to try to catch this at but the problem is that even on a memory limit reached sometimes that exit code is not properly returned and some random things happened. Actually, I think that I added that look for Due those random situations is that we don't have a good solution yet. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I think we can close this issue for now since there is not much else we can do to catch when a memory limit was reached. If we have a plan to reach this goal, we should write it down here and re-open the issue. |
Details
In some cases the build fails due to memory limits, but there isn't a clear message of what happened (I think I see some few projects with the correct message, or maybe none?).
See #3031, #3603, #3612, #3580
Expected Result
A message about memory limit is shown.
Actual Result
A plain message "Build failed" is shown.
I'm not sure if we can catch this types of errors on the environment.
The text was updated successfully, but these errors were encountered: