Renovate either failing, or succeeding but actually failing #36208
Replies: 2 comments 9 replies
-
We have the ability to boost resources for OSS projects, which is probably the easiest thing to do in this case. Please stay tuned |
Beta Was this translation helpful? Give feedback.
9 replies
-
Hi there, Please stick to one topic/question per Discussion. Start a new discussion per topic. This prevents future users from finding this discussion and getting confused by multiple questions and answers. One question and answer per Discussion works best. For example:
Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
A Mend.io-hosted app
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
I have Renovate configured on https://github.com/pachli/pachli-android for the past several years, and it's been working very well.
However, recently it's either been failing (as reported by the dashboard at https://developer.mend.io/github/pachli/pachli-android) or succeeding, but if you dig in to the logs it's actually failing reporting a "temporary error" because something is receiving SIGTERM.
There's no indication of any problems on the Renovate dashboard in the GitHub issue it maintains (pachli/pachli-android#99), you have to click through to the hosted Renovate dashboard.
The failures are
kernel-out-of-memory
, and the Renovate dashboard does report it's using 3GB of a 3GB limit. However, it's not clear when this started (the available logs don't go back very far), and I don't think the app has an unusual set of dependencies for a typical Android app.This may be related to pachli/pachli-android#1494 which introduced Gradle dependency verification. I could see how that might cause Renovate to require additional resources, but it's a bit concerning if (for open source projects, and to be clear, thank you for making this service available for free) the choice is easy update tracking with Renovate or improved dependency checksum and signature verification.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions