Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # dev - Re: Build failed in Jenkins: HBase-TRUNK #3498


Copy link to this message
-
Re: Build failed in Jenkins: HBase-TRUNK #4047
Stack 2013-04-10, 20:03
On Wed, Apr 10, 2013 at 12:04 PM, Nicolas Liochon <[EMAIL PROTECTED]> wrote:

> When you do install, it implies verify.
> And using 'mvn install' makes sense as it more or less needed when using
> maven multimodules.
> What we could do is something like "mvn clean install -DskipTests && mvn
> test"
>
>
There is also -DskipIntegrationTests  Let me try it and update doc
accordingly (I did not realize that mvn verify was implied by mvn install
-- ugh... that  immutable, ineluctable lifecycle of mvns must have been
made for mickey mouse projects....).

St.Ack

> On Wed, Apr 10, 2013 at 8:43 PM, Sergey Shelukhin <[EMAIL PROTECTED]
> >wrote:
>
> > I think it.test is needed to package them properly.
> > What causes them to be executed in the first place? Do we now have verify
> > step? Wasn't the case before.
> >
> > On Wed, Apr 10, 2013 at 9:38 AM, Stack <[EMAIL PROTECTED]> wrote:
> >
> > > On Wed, Apr 10, 2013 at 12:16 AM, Nicolas Liochon <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > > I don't know who added them actually. They're executed in 0.95 as
> well
> > I
> > > > think: they are executed with mvn install.
> > > > They seem to need ~1 hour to run and failed 2 of the last 10 builds
> (so
> > > > they fail 33% of the time when they are executed).
> > > >
> > > > For now, on trunk, I removed them by setting a dummy value to
> it.test.
> > > >
> > > >
> > > Thanks N.  I did the same in 0.95.  I filed
> > > https://issues.apache.org/jira/browse/HBASE-8319 to figure how to turn
> > > them
> > > off again so they are not inline w/ general unit test suite.
> > >
> > >
> > >
> > > > On the long term, the best option I see is to set another build,
> > > depending
> > > > on trunk, to execute them. This would save some time on the main
> build,
> > > > make the main build consistent with the precommit one, while still
> > having
> > > > the ITests running often
> > > >
> > > >
> > > Yes.
> > >
> > > St.Ack
> > >
> >
>