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
Abort repo when out of disk space message found in artifact update error #16536
Comments
BTW this will be rather hard to reproduce, so we will need to just code review it instead. |
Hi there, Get your issue fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. To get started, please read our guide on creating a minimal reproduction. We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment. Good luck, The Renovate team |
our team will try to reproduce in order to get more context |
I think a simple and quicker fix based on the log should be fine. Otherwise you would also be contributing to the app's load. It takes a multi GB project to use up the disk |
we thought we might be able to reproduce using docker while limiting it's space on self hosted, then we can have better context about what is the Actual vs the Expected results what i understand for the expected result is : log the error and stop the run? |
Yes warn and stop the repo run, instead of continuing to every branch and getting the same error |
After trying to reproduce this issue using VM with disk space limitation,
reproduction steps:
|
It's similar but not the same error |
Tried to make it fail during git clone, and I got these Logs:
|
🎉 This issue has been resolved in version 32.153.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What would you like Renovate to be able to do?
Catch yarn out of disk space errors during branch updates
If you have any ideas on how this should be implemented, please tell us here.
Here's an example "Error updating branch" error:
I think if we look for the string
write error. Out of diskspace
in an artifact error then we should then abort if we find it.Is this a feature you are interested in implementing yourself?
No
The text was updated successfully, but these errors were encountered: