You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure it will help to increase the limit, as some of the killed jobs show that they are running for 5+ hours. We can try to increase the limit and see whether we are only exceeding it by very little. Otherwise I think we will need to evaluate what's causing the builds to take forever and work on a better solution.
The fact that many builds are currently failing (and being re-built) because of problems with our Jenkins ironically puts even more load on the systems, so the effect seems to amplify.
The text was updated successfully, but these errors were encountered:
I took the liberty to test/increase the timeout in my PR, as it keeps hitting this limit. Seems like it is usually a build on a7 (which is slower) and I have not yet seen it on v2 (which is presumably faster).
The following build message occurred in multiple PRs I have seen (e.g. #3150):
It seems that we are increasingly hitting the 10 minute Jenkins limit (when a build has no log output for 10 minutes).
libelektra/scripts/jenkins/Jenkinsfile
Line 1271 in 6aea503
I'm not sure it will help to increase the limit, as some of the killed jobs show that they are running for 5+ hours. We can try to increase the limit and see whether we are only exceeding it by very little. Otherwise I think we will need to evaluate what's causing the builds to take forever and work on a better solution.
The fact that many builds are currently failing (and being re-built) because of problems with our Jenkins ironically puts even more load on the systems, so the effect seems to amplify.
The text was updated successfully, but these errors were encountered: