Core dump generated (git gc) and renovate adds core dump to commit #33817
Replies: 2 comments 1 reply
-
|
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsRead the Renovate docs, troubleshooting, self-hosted to learn how to find the logs. Insufficient logsSelect me to read instructionsIf you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section. Formatting your logsSelect me to read instructionsPlease put your logs in a If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
|
Renovate does not run |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @rarkins - I'll see what I can dig up. We did run the core dump through |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Gitea, renovate version 39.91.1
Please tell us more about your question or problem
Renovate created a commit which contained a core dump.
The core dump appeared to be from a
git gccommand which presumably was run by renovate before the commit was created. It terminated with aSIGABRTso I guess it was a memory allocation issue. The core dump was generated in the same directory as the git repo and when the commit was created, it was added to the commit.For this specific case, we allowed renovate to merge the commit automatically, so it just appeared in our repo.
It would be good to have a way to control the behaviour here - is there a way to control what happens if
git gcdumps like this?Logs (if relevant)
Will try to obtain logs.
Core dump analysis (issues with loading so's are because I'm running on NixOS)
No response
Beta Was this translation helpful? Give feedback.
All reactions