falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Srikanth Sundarrajan <srik...@hotmail.com>
Subject RE: Jenkins build failures for Apache Falcon
Date Fri, 22 Jul 2016 10:47:07 GMT
I agree. We can classify tests and run critical ones for pre-commit and the more elaborate
ones nightly. IIRC, there is already a JIRA pending on this (probably for a very long time)
RegardsSrikanth Sundarrajan

> From: ajayyadavaatos@gmail.com
> Date: Fri, 22 Jul 2016 10:30:49 +0000
> Subject: Re: Jenkins build failures for Apache Falcon
> To: dev@falcon.apache.org
> 
> I am of the opinion that such tests are more suitable for regression. These
> tests take lot of time and make running tests locally or debugging them a
> huge pain. We built falcon-unit for such cases but adoption is very low and
> even in that we have seen large time outs. Tests which have time outs of 10
> seconds are not suitable for pre commit checks.
> 
> It also creates a bad entry barrier for new users / contributors to just
> download the source and run all tests locally. We should probably schedule
> a nightly / weekly build of regression and that will be more thorough and
> helpful in such scenarios.
> 
> 
> 
> 
> 
> On Fri, Jul 22, 2016 at 10:30 AM Ying Zheng <yzheng@hortonworks.com> wrote:
> 
> > +1.
> >
> > On 7/21/16, 9:34 PM, "Venkat Ranganathan" <vranganathan@hortonworks.com>
> > wrote:
> >
> > >Thanks Srikanth for giving access to Balu.    Last time I looked at the
> > >jobs, there seems to be a dependency on the specific host where it was
> > >running.   Trying to move it another host was not helpful.  May be we
> > >make it run on a pool of machines than one as it is currently done
> > >
> > >Venkat
> > >
> > >On 7/21/16, 6:58 PM, "Srikanth Sundarrajan" <sriksun@hotmail.com> wrote:
> > >
> > >    Hi Balu,Physical access to the machine may be harder. But it is
> > >possible to modify the jenkins job to put out any logs from the build
> > >apart from the binaries it produces. Hopefully that should allow us to
> > >debug this issue. I can either make changes you seek to the build or give
> > >you permissions to modify the job yourself. The later may be a better
> > >choice.
> > >    RegardsSrikanth Sundarrajan
> > >
> > >    > Subject: Jenkins build failures for Apache Falcon
> > >    > From: bvellanki@hortonworks.com
> > >    > To: dev@falcon.apache.org
> > >    > Date: Thu, 21 Jul 2016 23:30:08 +0000
> > >    >
> > >    > Hi Team,
> > >    >
> > >    > Recently, builds are failing for Apache Falcon (Email Ref : Build
> > >failed
> > >    > in Jenkins: Apache-falcon #1064). The tests that fail require
> > >instances
> > >    > scheduled in workflow engine to reach a certain state like RUNNING
> > >or
> > >    > SUCCEEDED. But the instances seem to be stuck in state WAITING even
> > >after
> > >    > delays of up to 10 seconds.
> > >    >
> > >    > The same tests do not fail in local environment. The machine running
> > >    > Jenkins builds does not seem to have enough resources. I request
> > >access to
> > >    > the machine for further debugging and adjusting resource allocation
> > >OR
> > >    > will accept help from some one who has access to the machine.
> > >    >
> > >    > Please let me know,
> > >    > Thank you
> > >    > Balu Vellanki
> > >    >
> > >
> > >
> >
> > --
> Regards
> Ajay Yadava
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message