> Scott: > Do you have time to write a script for analyzing output of Jenkins and put > it on HBASE-4480 ?
I'll take a shot and post something on 4480. > Here is some idea from Ramkrishna: > > All statements that has Running in it can be parsed to see if the every > next > Running happens after one hop. > Like if the first Running happens to be in 11th line the next Running > should > be in 13th. > If this breaks some where then that test is hanging. If you come across one of these examples in the next day or so, please send it to me. > This is just one idea. If we can figure out something better we can take > it > up. > > Cheers > > On Sat, Oct 8, 2011 at 9:53 AM, Jesse Yates <jesse.k.ya...@gmail.com> > wrote: > >> The script to do this was written in 4480. Just needs some +1s a >> - It works pretty well. >> >> We might want to also mod it to take in a file that is the output of a >> run >> and analyze that. >> >> - Jesse Yates >> >> Sent from my iPhone. >> >> On Oct 8, 2011, at 2:51 AM, Ted Yu <yuzhih...@gmail.com> wrote: >> >> > Parsing test output will do. >> > >> > >> > >> > On Oct 7, 2011, at 11:44 PM, Akash Ashok <thehellma...@gmail.com> >> wrote: >> > >> >> Hi Ted & Ram >> >> >> >> Just Figured out the hung test case both in >> >> >> >> >> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2303/console >> >> >> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2304/console >> >> >> >> Running org.apache.hadoop.hbase.io.hfile.slab.TestSlabCache >> >> Running org.apache.hadoop.hbase.io.hfile.TestFixedFileTrailer >> >> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.858 >> sec >> >> >> >> TestSlabCache is the culprit >> >> >> >> Just copied into noteped++ and searched for running and it >> highlighted >> it >> >> and it was easier to find :) >> >> >> >> And about the script. Is the idea to parse this output and figure out >> the >> >> hung test case or is there a plan to parse the surefire reports xml? >> >> >> >> Cheers, >> >> Akash A >> >> >> >> On Sat, Oct 8, 2011 at 11:13 AM, Ted Yu <yuzhih...@gmail.com> wrote: >> >> >> >>> Yeah we need such script. >> >>> I went over the tests in >> >>> >> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2303/console >> >>> and couldn't find out the hanging test. >> >>> >> >>> Cheers >> >>> >> >>> On Fri, Oct 7, 2011 at 10:33 PM, Ramakrishna S Vasudevan 00902313 < >> >>> ramakrish...@huawei.com> wrote: >> >>> >> >>>> Ted >> >>>> >> >>>> Once we were already discussing regarding some script to find out >> some >> >>> hung >> >>>> tests? >> >>>> >> >>>> Regards >> >>>> Ram >> >>>> >> >>>> >> >>>> ----- Original Message ----- >> >>>> From: Ted Yu <yuzhih...@gmail.com> >> >>>> Date: Saturday, October 8, 2011 10:58 am >> >>>> Subject: Re: Jenkins build is back to normal : HBase-TRUNK #2304 >> >>>> To: dev@hbase.apache.org >> >>>> >> >>>>> From >> >>>>> https://builds.apache.org/view/G-L/view/HBase/job/HBase- >> >>>>> TRUNK/2303/console,it wasn't obvious which test(s) hung. >> >>>>> But the following error clearly indicated there was some hanging >> Java >> >>>>> process: >> >>>>> >> >>>>> [ERROR] Failed to execute goal >> >>>>> org.apache.maven.plugins:maven-surefire-plugin:2.9:test >> (default-test) >> >>>>> on project hbase: Failure or timeout -> [Help >> >>>>> 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed >> to >> >>>>> execute goal >> org.apache.maven.plugins:maven-surefire-plugin:2.9:test >> >>>>> (default-test) on project hbase: Failure or timeout >> >>>>> >> >>>>> Unluckily we don't have access to the build machine. >> >>>>> >> >>>>> On Fri, Oct 7, 2011 at 10:14 PM, Akash Ashok >> >>>>> <thehellma...@gmail.com> wrote: >> >>>>> >> >>>>>> Oh cool. Build is back to normal. Could someone tell me what the >> >>>>> issue was. >> >>>>>> Why was it failing even though there were no failures ? >> >>>>>> >> >>>>>> On Sat, Oct 8, 2011 at 4:45 AM, Apache Jenkins Server < >> >>>>>> jenk...@builds.apache.org> wrote: >> >>>>>> >> >>>>>>> See <https://builds.apache.org/job/HBase-TRUNK/2304/> >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>> >> >>>>> >> >>>> >> >>> >> >
