You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Appy (JIRA)" <ji...@apache.org> on 2017/11/30 01:56:00 UTC

[jira] [Commented] (HBASE-19382) Update report-flakies.py script to handle yetus builds

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

Appy commented on HBASE-19382:
------------------------------

Tested it locally. Output below. Dashboard also looks right.
{noformat}
appy appy-MBP-3 ~/apache/hbase (update_report_flakies) → dev-support/report-flakies.py --mvn -v --urls=https://builds.apache.org/job/HBASE-Flaky-Tests/ --max-builds=10 --is-yetus=False --urls="https://builds.apache.org/job/HBase%20Nightly/job/master/" --max-builds=3 --is-yetus=True
INFO:__main__:Analyzing job: https://builds.apache.org/job/HBASE-Flaky-Tests/
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23616/
INFO:__main__:Skipping this build since it is in progress.
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23615/
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Result > total tests:   65   failed :    5  timedout :    0  hanging :    3
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23614/
Result > total tests:   65   failed :    9  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23613/
Result > total tests:   61   failed :    6  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23612/
Result > total tests:   61   failed :    4  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23611/
Result > total tests:   61   failed :    6  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23610/
Result > total tests:   61   failed :    8  timedout :    0  hanging :    1
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23609/
Result > total tests:   61   failed :    6  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23608/
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Result > total tests:   62   failed :    5  timedout :    0  hanging :    3
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23607/
Result > total tests:   62   failed :    7  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBASE-Flaky-Tests/23606/
Result > total tests:   60   failed :    6  timedout :    0  hanging :    0
URL: https://builds.apache.org/job/HBASE-Flaky-Tests/
                                                   Test Name  Total Runs  Bad Runs(failed/timeout/hanging)  Flakyness
                 master.procedure.TestTruncateTableProcedure          10       10 (   10 /     0 /     0 )  100%
                               client.TestReplicaWithCluster          10        9 (    9 /     0 /     0 )  90%
                  regionserver.TestSplitTransactionOnCluster          10        8 (    7 /     0 /     1 )  80%
               regionserver.TestCompactionInDeadRegionServer          10        8 (    8 /     0 /     0 )  80%
                     master.assignment.TestAssignmentManager          10        5 (    5 /     0 /     0 )  50%
                                 client.TestMetaWithReplicas          10        4 (    4 /     0 /     0 )  40%
             master.assignment.TestSplitTableRegionProcedure          10        3 (    3 /     0 /     0 )  30%
                          client.TestBlockEvictionFromClient          10        3 (    3 /     0 /     0 )  30%
           master.procedure.TestMasterFailoverWithProcedures          10        3 (    3 /     0 /     0 )  30%
                                        rsgroup.TestRSGroups          10        3 (    2 /     0 /     1 )  30%
                         master.TestAssignmentManagerMetrics           9        2 (    2 /     0 /     0 )  22%
                                           client.TestAdmin2          10        2 (    0 /     0 /     2 )  20%
                                              client.TestHCM          10        2 (    0 /     0 /     2 )  20%
                            regionserver.TestFSErrorsExposed          10        2 (    2 /     0 /     0 )  20%
           master.balancer.TestFavoredStochasticLoadBalancer          10        1 (    1 /     0 /     0 )  10%
                          master.TestDistributedLogSplitting          10        1 (    1 /     0 /     0 )  10%
                      security.token.TestTokenAuthentication          10        1 (    0 /     0 /     1 )  10%
                                   client.TestReplicasClient          10        1 (    1 /     0 /     0 )  10%
                                  quotas.TestQuotaStatusRPCs          10        1 (    1 /     0 /     0 )  10%
Builds analyzed: [23606, 23607, 23608, 23609, 23610, 23611, 23612, 23613, 23614, 23615]
Builds without any test runs: []

INFO:__main__:Analyzing job: https://builds.apache.org/job/HBase%20Nightly/job/master/
INFO:__main__:Analyzing https://builds.apache.org/job/HBase%20Nightly/job/master/144/
ERROR! Multiple tests with same name 'util.TestPoolMap$TestRoundRobinPoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestRoundRobinPoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! Multiple tests with same name 'util.TestPoolMap$TestReusablePoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestReusablePoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! Multiple tests with same name 'util.TestPoolMap$TestThreadLocalPoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestThreadLocalPoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'master.TestCatalogJanitor' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'regionserver.TestRegionServerReadRequestMetrics' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'client.TestReplicaWithCluster' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
Result > total tests:  871   failed :    3  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBase%20Nightly/job/master/143/
ERROR! Multiple tests with same name 'util.TestPoolMap$TestRoundRobinPoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestRoundRobinPoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! Multiple tests with same name 'util.TestPoolMap$TestReusablePoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestReusablePoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! Multiple tests with same name 'util.TestPoolMap$TestThreadLocalPoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestThreadLocalPoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'quotas.TestSnapshotQuotaObserverChore' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Result > total tests:  778   failed :    2  timedout :    0  hanging :    0
INFO:__main__:Analyzing https://builds.apache.org/job/HBase%20Nightly/job/master/142/
ERROR! Multiple tests with same name 'util.TestPoolMap$TestRoundRobinPoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestRoundRobinPoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! Multiple tests with same name 'util.TestPoolMap$TestReusablePoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestReusablePoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! Multiple tests with same name 'util.TestPoolMap$TestThreadLocalPoolType'. Might get wrong results for this test.
ERROR! No test 'util.TestPoolMap$TestThreadLocalPoolType' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'replication.regionserver.TestTableBasedReplicationSourceManagerImpl' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'replication.regionserver.TestTableBasedReplicationSourceManagerImpl' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'coprocessor.TestRegionObserverInterface' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
ERROR! No test 'client.TestReplicaWithCluster' found in hanging_tests. Might get wrong results for this test. This may also happen if maven is set to retry failing tests.
Bad string found in build:
 > [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Bad string found in build:
 > [ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Result > total tests:  778   failed :    4  timedout :    0  hanging :    1
URL: https://builds.apache.org/job/HBase%20Nightly/job/master/
                                                   Test Name  Total Runs  Bad Runs(failed/timeout/hanging)  Flakyness
                               client.TestReplicaWithCluster           3        3 (    3 /     0 /     0 )  100%
replication.regionserver.TestTableBasedReplicationSourceManagerImpl           3        1 (    1 /     0 /     0 )  33%
             master.assignment.TestSplitTableRegionProcedure           3        1 (    1 /     0 /     0 )  33%
                       quotas.TestSnapshotQuotaObserverChore           3        1 (    1 /     0 /     0 )  33%
                                   master.TestCatalogJanitor           3        1 (    1 /     0 /     0 )  33%
             regionserver.TestRegionServerReadRequestMetrics           3        1 (    1 /     0 /     0 )  33%
                     coprocessor.TestRegionObserverInterface           3        1 (    1 /     0 /     0 )  33%
security.visibility.TestVisibilityLabelsWithCustomVisLabService           3        1 (    0 /     0 /     1 )  33%
Builds analyzed: [142, 143, 144]
Builds without any test runs: []
{noformat}

> Update report-flakies.py script to handle yetus builds
> ------------------------------------------------------
>
>                 Key: HBASE-19382
>                 URL: https://issues.apache.org/jira/browse/HBASE-19382
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Appy
>            Assignee: Appy
>         Attachments: HBASE-19382.master.001.patch
>
>
> With move to new nightly build which uses yetus (https://builds.apache.org/job/HBase%20Nightly/job/master/), current report-flakies.py is not able to build test report since maven output is not in consoleText anymore. Update script to accept both traditional builds (maven output in consoleTest, for flakies runner job)  and yetus builds (maven output in artifacts).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)