-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Keep the command's output when it's killed #4957
Comments
This would be very useful :) right now I need to blindly reduce the size of my example, make another pull request, rerun the build and hope :) |
I suppose the reason why we put this pre-defined output is that when the command is killed, we don't get any output in return from docker. |
Interesting, I'll try to reproduce that locally and see |
So, after some attempts, I was able to reproduce and catch locally, this is what I found
We have some output, it may be helpful for debugging, and there is a I'm going to keep investigating if there are some side effects. |
Hi, I thought this was merged? |
I have tried to even rebuild the stable version which points to a commit at tag v1.1.0. If this built at some point I don't see how it is possible that it is not building anymore due to 'excessive memory consumption'. Do you sometimes grab bigger nodes than other times for the built in docker? |
This isn't deployed yet
Sometimes the builders are very busy, so if your project needs a lot of resources it could fail. |
When a command is killed because of memory consumption we replace the output with a message
https://github.com/rtfd/readthedocs.org/blob/85d9a1fb236e2c2149358b1cf462159e523e80bb/readthedocs/doc_builder/environments.py#L274-L276
the output can be helpful to users to debug the build. I guess we should only show the error about the memory in the top? Or maybe just concatenated the output with that msg?
Raised in #4946 (comment)
Related to #4468
The text was updated successfully, but these errors were encountered: