This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
Increase build timeout of coverage builds by 5 min #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This trend shows that coverage builds tend to take close to 20min and we regularly run into timeouts: https://ci.centos.org/job/devtools-almighty-core-coverage/buildTimeTrend
aslakknutsen
approved these changes
Jan 25, 2017
|
I'm still facing failures @kbsingh @kwk . |
|
@sbose78 non of the past failing tests lasted longer than 20 min so I guess my change to 25 timeout wasn't deployed when I started the old build. I've started another one just moments ago: fabric8-services/fabric8-wit#655 (comment) . Let's see if that works. |
|
@sbose78 Problem is fixed and coverage build finished in 21 minutes https://ci.centos.org/job/devtools-almighty-core-coverage/195/ |
|
Thank you so much for your help @kwk ! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This trend shows that coverage builds for core tend to take close to 20min and we regularly run into timeouts: https://ci.centos.org/job/devtools-almighty-core-coverage/buildTimeTrend . That's why I want to increase the build timeout by 5 minutes.
@sbose78 has already written an email about this: https://www.redhat.com/archives/almighty-public/2017-January/msg00036.html