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 <wstev...@cloudops.com> 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 > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > w cloudops.com *|* tw @CloudOps_ > > On Wed, Apr 6, 2016 at 4:29 PM, Will Stevens <wstev...@cloudops.com> > wrote: > > > 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, 2016 at 4:28 PM, Will Stevens <wstev...@cloudops.com> > > wrote: > > > >> 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 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > >> w cloudops.com *|* tw @CloudOps_ > >> > >> On Wed, Apr 6, 2016 at 4:17 PM, Daan Hoogland <daan.hoogl...@gmail.com> > >> wrote: > >> > >>> I've seen this one before: > >>> > >>> Tests in error: > >>> SecondaryStorageManagerTest.getDefaultNetworkForAdvancedNonSG:79 > >>> NoSuchMethod ... > >>> SecondaryStorageManagerTest.getDefaultNetworkForAdvancedSG:102 > >>> NoSuchMethod or... > >>> SecondaryStorageManagerTest.getDefaultNetworkForAdvancedWrongZoneType > >>> ? Unexp... > >>> SecondaryStorageManagerTest.getDefaultNetworkForBasicNonSG:124 > >>> NoSuchMethod or... > >>> SecondaryStorageManagerTest.getDefaultNetworkForBasicSG:147 > >>> NoSuchMethod org.a... > >>> SecondaryStorageManagerTest.getDefaultNetworkForBasicSGWrongZoneType > >>> ? Unexpe... > >>> > >>> > >>> it has been a reason of failure in more then one. > >>> > >>> > >>> > >>> On Wed, Apr 6, 2016 at 10:13 PM, Daan Hoogland < > daan.hoogl...@gmail.com> > >>> wrote: > >>> > >>> > 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 < > williamstev...@gmail.com > >>> > > >>> > wrote: > >>> > > >>> >> 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 > >>> >> > >>> > > >>> > > >>> > > >>> > -- > >>> > Daan > >>> > > >>> > >>> > >>> > >>> -- > >>> Daan > >>> > >> > >> > > > -- Rafael Weingärtner
