hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Liochon <nkey...@gmail.com>
Subject Re: Anyone know how to get surefire to list timed out tests?
Date Tue, 09 Apr 2013 08:51:01 GMT
I don't know how to do that automatically (except some workarounds such as
the one above but they don't always work).

Manually, it's not too difficult, as the report (
http://54.241.6.143/job/HBase-0.94/org.apache.hbase$hbase/71/testReport/)
tells you the number of missing tests compared to the previous build per
package.
Once you have the package, the list is usually small, and comparing with
the previous report becomes possible. In the example above, it's
TestSizeBasedThrottler  for example.

Yes, I know, it's not an industrial solution...



On Tue, Apr 9, 2013 at 5:20 AM, Ted Yu <yuzhihong@gmail.com> wrote:

> A little parsing is needed:
>       ZB_STACK=`jps | grep surefirebooter | cut -d ' ' -f 1 | xargs -n 1
> jstack | grep ".test" | grep "\.java"`
>
> On Mon, Apr 8, 2013 at 8:14 PM, Andrew Purtell <apurtell@apache.org>
> wrote:
>
> > I just checked and the test name isn't embedded in the jps output. Will
> try
> > running with mvn -X instead.
> >
> >
> >
> > On Mon, Apr 8, 2013 at 8:12 PM, Andrew Purtell <apurtell@apache.org>
> > wrote:
> >
> > > Thanks Ted. Good idea.
> > >
> > >
> > > On Mon, Apr 8, 2013 at 8:06 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> > >
> > >> Andy:
> > >> Have you looked at how dev-support/test-patch.sh finds zombie tests ?
> > >> It starts from line 659:
> > >>
> > >>   ZOMBIE_TESTS_COUNT=`jps | grep surefirebooter | wc -l`
> > >>   if [[ $ZOMBIE_TESTS_COUNT != 0 ]] ; then
> > >>
> > >> Cheers
> > >>
> > >> On Mon, Apr 8, 2013 at 7:09 PM, Andrew Purtell <apurtell@apache.org>
> > >> wrote:
> > >>
> > >> > I set up a freestyle project to build by invoking maven out of a
> shell
> > >> > script. My guess is that will show the timed out tests as happens
> when
> > >> run
> > >> > locally in a terminal. See
> > http://54.241.6.143/job/HBase-0.94-Freestyle
> > >> >
> > >> >
> > >> > On Mon, Apr 8, 2013 at 5:45 PM, Andrew Purtell <apurtell@apache.org
> >
> > >> > wrote:
> > >> >
> > >> > > See for example http://54.241.6.143/job/HBase-0.94/71/console:
> > >> > >
> > >> > > [...]
> > >> > > [JENKINS] Recording test results
> > >> > > [INFO]
> > >> > >
> > >>
> ------------------------------------------------------------------------
> > >> > > [INFO] BUILD FAILURE
> > >> > > [INFO]
> > >> > >
> > >>
> ------------------------------------------------------------------------
> > >> > > [INFO] Total time: 1:18:06.862s
> > >> > > [INFO] Finished at: Mon Apr 08 08:10:20 UTC 2013
> > >> > > [INFO] Final Memory: 32M/501M
> > >> > > [INFO]
> > >> > >
> > >>
> ------------------------------------------------------------------------
> > >> > > [JENKINS] Archiving
> > >> /home/ec2-user/jenkins/workspace/HBase-0.94/pom.xml
> > >> > to
> > >> > >
> > >> >
> > >>
> >
> /var/lib/jenkins/jobs/HBase-0.94/modules/org.apache.hbase$hbase/builds/2013-04-08_06-52-05/archive/org.apache.hbase/hbase/0.94.6/hbase-0.94.6.pom
> > >> > > Waiting for Jenkins to finish collecting data
> > >> > > mavenExecutionResult exceptions not empty
> > >> > > message : Failed to execute goal
> > >> > >
> > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test
> > >> > > (secondPartTestsExecution) on project hbase: Failure or timeout
> > >> > > cause : Failure or timeout
> > >> > > Stack trace :
> > >> > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed
to
> > >> execute
> > >> > > goal
> > >> >
> org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test
> > >> > > (secondPartTestsExecution) on project hbase: Failure or timeout
> > >> > > [unhelpful big stacktrace]
> > >> > > channel stopped
> > >> > > Sending e-mails to: dev@hbase.apache.org
> > >> > > Finished: FAILURE
> > >> > >
> > >> > > It would be fantastic if the test(s) which timed out were listed
> > >> somehow
> > >> > > here.
> > >> > >
> > >> > > --
> > >> > > Best regards,
> > >> > >
> > >> > >    - Andy
> > >> > >
> > >> > > Problems worthy of attack prove their worth by hitting back.
-
> Piet
> > >> Hein
> > >> > > (via Tom White)
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Best regards,
> > >> >
> > >> >    - Andy
> > >> >
> > >> > Problems worthy of attack prove their worth by hitting back. - Piet
> > Hein
> > >> > (via Tom White)
> > >> >
> > >>
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > >    - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> > >
> >
> >
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message