exec interrupted by SIGTERM #29961
Unanswered
jkananen
asked this question in
Request Help
Replies: 2 comments 10 replies
|
The logs are missing necessary metadata (only the message is showing) |
8 replies
|
I'm seeing something similar with Poetry runs: I'm happy to open a new discussion or issue for this if it appears to have a different cause. |
2 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.
Uh oh!
There was an error while loading. Please reload this page.
What would you like help with?
I think I found a bug
How are you running Renovate?
Mend Renovate hosted app on github.com
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
For two weeks now, all (?) of our renonate runs have failed with:
The last successful job ID is:
01902611-a595-749b-bfeb-205c198b405don 17 Jun 2024, 14:17:00.The first failed job ID is
019026b6-b9be-7cf8-947d-cfd1c8fd3fbfon 17 Jun 2024, 17:25:41.I've compared the logs side by side, and here's where they start to differ:
DEBUG: syncBranchState(): Branch cache not found, creating minimal branchStateSoon thereafter, the failed run's log says:
The last successful run has lasted 1m 6s, whereas failed runs last 18-19 minutes. I've seen somewhere that failures are expected if
yarn installruns over 15 minutes. It's a monorepo that we have and allpackage.jsonfiles have"packageManager": "yarn@3.8.2"defined.Any thoughts if this is a configuration issue on our side or if renovate is failing for some internal reason? Note that there are no new commits in our repository on the day when the failed runs have started (Mon, June 17th).
Thanks in advance for any assistance!
Logs (if relevant)
Logs
All reactions