hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8018) Add "Flaky Testcase Detector" tool into dev-tools
Date Sun, 11 Aug 2013 08:45:48 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736237#comment-13736237
] 

Hudson commented on HBASE-8018:
-------------------------------

SUCCESS: Integrated in hbase-0.95 #431 (See [https://builds.apache.org/job/hbase-0.95/431/])
hbase-8018: Add 'Flaky Testcase Detector' tool into dev-tools (jeffreyz: rev 1512879)
* /hbase/branches/0.95/dev-support/jenkins-tools
* /hbase/branches/0.95/dev-support/jenkins-tools/README.md
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/pom.xml
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase/devtools
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase/devtools/buildstats
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase/devtools/buildstats/BuildResultWithTestCaseDetails.java
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase/devtools/buildstats/HistoryReport.java
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase/devtools/buildstats/TestCaseResult.java
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase/devtools/buildstats/TestResultHistory.java
* /hbase/branches/0.95/dev-support/jenkins-tools/buildstats/src/main/java/org/apache/hadoop/hbase/devtools/buildstats/TestSuite.java
* /hbase/branches/0.95/dev-support/jenkins-tools/pom.xml

                
> Add "Flaky Testcase Detector" tool into dev-tools
> -------------------------------------------------
>
>                 Key: HBASE-8018
>                 URL: https://issues.apache.org/jira/browse/HBASE-8018
>             Project: HBase
>          Issue Type: Bug
>          Components: util
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 0.98.0, 0.95.2
>
>         Attachments: hbase-8018.patch, hbase-8018-v1.patch, hbase-8018-v2.patch, hbase-8018-v3.patch,
hbase-8018-v4.patch
>
>
> jenkins-tools
> =============
> A tool which pulls test case results from Jenkins server. It displays a union of failed
test cases 
> from the last 15(by default and actual number of jobs can be less depending on availablity)
runs 
> recorded in Jenkins sever and track how each of them are performed for all the last 15
runs(passed, 
> not run or failed)
> *Pre-requirement(run under folder jenkins-tools)*
>        Please download jenkins-client from https://github.com/cosmin/jenkins-client
>        1) git clone git://github.com/cosmin/jenkins-client.git
>        2) make sure the dependency jenkins-client version in ./buildstats/pom.xml matches
the 
>           downloaded jenkins-client(current value is 0.1.6-SNAPSHOT)
>        
> Build command(run under folder jenkins-tools):
> {code}
>        mvn clean package
> {code}
> Usage are: 
> {code}
>        java -jar ./buildstats/target/buildstats.jar <Jenkins HTTP URL> <Job
Name> [number of last most recent jobs to check]
> {code}
> Sample commands are:
> {code}
>        java -jar ./buildstats/target/buildstats.jar https://builds.apache.org HBase-TRUNK
> {code}
> Sample output(where 1 means "PASSED", 0 means "NOT RUN AT ALL", -1 means "FAILED"):
> Failed Test Cases Stats        4360 4361 4362 4363 4364 4365 4366 4367 4368 4369
> ========================================================
> org.apache.hadoop.hbase.backup.testhfilearchiving.testcleaningrace    1    1    1   
1    1    1    1    1   -1    0
> org.apache.hadoop.hbase.migration.testnamespaceupgrade.testrenameusingsnapshots    1
   1    1   -1    0    1    1    1    1    1
> Skipped Test Cases Stats
> ======= 4360 skipped(Or don't have) following test suites =======
> org.apache.hadoop.hbase.replication.testreplicationkillmasterrscompressed
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfilessplitrecovery
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfiles
> org.apache.hadoop.hbase.mapreduce.testmapreduceexamples
> ======= 4361 skipped(Or don't have) following test suites =======
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfilessplitrecovery
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfiles
> org.apache.hadoop.hbase.mapreduce.testmapreduceexamples
> ======= 4362 skipped(Or don't have) following test suites =======
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfilessplitrecovery
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfiles
> org.apache.hadoop.hbase.mapreduce.testmapreduceexamples
> ======= 4363 skipped(Or don't have) following test suites =======
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfilessplitrecovery
> org.apache.hadoop.hbase.mapreduce.testsecureloadincrementalhfiles
> org.apache.hadoop.hbase.mapreduce.testmapreduceexamples
> ======= 4368 skipped(Or don't have) following test suites =======
> org.apache.hadoop.hbase.client.testadmin
> org.apache.hadoop.hbase.client.testclonesnapshotfromclient
> org.apache.hadoop.hbase.mapreduce.testmapreduceexamples

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message