Since > 38.40.1 renovate exits with status code 134 #30923
Unanswered
otbe
asked this question in
Request Help
Replies: 2 comments 2 replies
-
Try googling that error |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hi there, You're reporting a problem with an old version of Renovate. Please try the latest version and tell us if that fixes your problem. Be sure to provide updated logs once you have run with a newer version. Good luck, 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
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Gitlab
Please tell us more about your question or problem
Somewhen after 38.40.1 a lot of renovate runs across different projects start to fail with
Command failed with exit code 134
I tested versions: 38.43.0 and 38.44.3
Its a run of a single repository with a moderate amount of dependencies (<50).
The annotation marks when something > 38.40.1 was deployed.
![Screenshot 2024-08-20 at 23 40 15](https://private-user-images.githubusercontent.com/3391052/359655626-0be24b2c-c72d-4743-bc32-289a41758264.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNzI1NTcsIm5iZiI6MTcyNjE3MjI1NywicGF0aCI6Ii8zMzkxMDUyLzM1OTY1NTYyNi0wYmUyNGIyYy1jNzJkLTQ3NDMtYmMzMi0yODlhNDE3NTgyNjQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MTJUMjAxNzM3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MTZhYjBmMzI3MmIwNjAzMWY3ZmMyMzk5ZjQ1YTlhMWNlYzY3YjkyNDAxZjhkNjFkYzk5MWE2NTQ2NDE4Njc1MiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.lGtWW47_m54WPI5Yvotkfvz3XSdDA5pjaP15PKOAXuA)
That means from ~10% memory usage (of 4GB), it went up to >50% after the deployment which also explains why the process is killed at some point.
Logs (if relevant)
The last log line before this happens is:
Logs
Beta Was this translation helpful? Give feedback.
All reactions