Re: Jenkins on PRs

2016-04-06 Thread Will Stevens
Ya, that is what I am doing... Thanks... *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Wed, Apr 6, 2016 at 4:53 PM, Daan Hoogland wrote: > basically this means you have to ask the submit

Re: Jenkins on PRs

2016-04-06 Thread Daan Hoogland
basically this means you have to ask the submitter, Will On Wed, Apr 6, 2016 at 10:43 PM, Will Stevens wrote: > ok, thanks... > > *Will STEVENS* > Lead Developer > > *CloudOps* *| *Cloud Solutions Experts > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > w cloudops.com *|* tw @CloudOps_ > > On

Re: Jenkins on PRs

2016-04-06 Thread Will Stevens
ok, thanks... *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Wed, Apr 6, 2016 at 4:37 PM, Daan Hoogland wrote: > strangely the timeout wasn't reached on those jobs. I upped the timeout > a

Re: Jenkins on PRs

2016-04-06 Thread Daan Hoogland
strangely the timeout wasn't reached on those jobs. I upped the timeout anyway. let's see what happens. On Wed, Apr 6, 2016 at 10:30 PM, Daan Hoogland wrote: > you are right, there are three of those in the preserved history. I will > look at the timeout configuration for the job. > > On Wed, Ap

Re: Jenkins on PRs

2016-04-06 Thread Rafael Weingärtner
I believe the easiest way is to add a new commit or a push -f to the pr On Wed, Apr 6, 2016 at 5:29 PM, Will Stevens wrote: > Is there a way to kick off a new Jenkins run on a PR that it had failed on > previously? > > *Will STEVENS* > Lead Developer > > *CloudOps* *| *Cloud Solutions Experts >

Re: Jenkins on PRs

2016-04-06 Thread Daan Hoogland
you are right, there are three of those in the preserved history. I will look at the timeout configuration for the job. On Wed, Apr 6, 2016 at 10:28 PM, Will Stevens wrote: > I have been seeing it fail more often than usual with "timeout" errors. > > For example, this PR: https://github.com/apac

Re: Jenkins on PRs

2016-04-06 Thread Will Stevens
Is there a way to kick off a new Jenkins run on a PR that it had failed on previously? *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Wed, Apr 6, 2016 at 4:29 PM, Will Stevens wrote: > The

Re: Jenkins on PRs

2016-04-06 Thread Will Stevens
The reason I bring it up is because I don't want to '--force' PR merges, but it wants PRs to have all green lights (obviously). *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Wed, Apr 6, 201

Re: Jenkins on PRs

2016-04-06 Thread Will Stevens
I have been seeing it fail more often than usual with "timeout" errors. For example, this PR: https://github.com/apache/cloudstack/pull/1461 With this run: https://builds.apache.org/job/cloudstack-pr-analysis/719/console *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 r

Re: Jenkins on PRs

2016-04-06 Thread Daan Hoogland
I've seen this one before: Tests in error: SecondaryStorageManagerTest.getDefaultNetworkForAdvancedNonSG:79 NoSuchMethod ... SecondaryStorageManagerTest.getDefaultNetworkForAdvancedSG:102 NoSuchMethod or... SecondaryStorageManagerTest.getDefaultNetworkForAdvancedWrongZoneType ? Unexp... S

Re: Jenkins on PRs

2016-04-06 Thread Daan Hoogland
looking at the history in [1] this is not true. most are succeeding. [1] https://builds.apache.org/view/All/job/cloudstack-pr-analysis/ On Wed, Apr 6, 2016 at 8:40 PM, Will Stevens wrote: > Hey All, > Anyone know what is going on with Jenkins? It seems to be failing for most > PRs. It seems

Jenkins on PRs

2016-04-06 Thread Will Stevens
Hey All, Anyone know what is going on with Jenkins? It seems to be failing for most PRs. It seems to be timing out, but I am not a Jenkins wizard... Cheers, Will