You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/10/02 21:16:27 UTC
[jira] [Updated] (HBASE-14543) Have findHangingTests.py dump more
info
[ https://issues.apache.org/jira/browse/HBASE-14543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-14543:
--------------------------
Attachment: 14543.patch
Some ugly hacking on your little python script. No one is allowed look at it because it so ugly. Here is what it dumps out now:
{code}
Fetching https://builds.apache.org/view/H-L/view/HBase/job/PreCommit-HBASE-Build/15839/consoleText
Building remotely on H7 (Mapreduce Falcon Hadoop Pig Zookeeper Tez Hdfs) in workspace /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build
Testing patch for HBASE-13819.
Testing patch on branch branch-1.
[INFO] Apache HBase ...................................... SUCCESS [2.840s]
[INFO] Apache HBase - Checkstyle ......................... SUCCESS [0.499s]
[INFO] Apache HBase - Resource Bundle .................... SUCCESS [0.170s]
[INFO] Apache HBase - Annotations ........................ SUCCESS [0.948s]
[INFO] Apache HBase - Protocol ........................... SUCCESS [11.783s]
[INFO] Apache HBase - Common ............................. SUCCESS [1:28.325s]
[INFO] Apache HBase - Procedure .......................... SUCCESS [1:54.765s]
[INFO] Apache HBase - Client ............................. SUCCESS [1:23.896s]
[INFO] Apache HBase - Hadoop Compatibility ............... SUCCESS [7.361s]
[INFO] Apache HBase - Hadoop Two Compatibility ........... SUCCESS [7.552s]
[INFO] Apache HBase - Prefix Tree ........................ SUCCESS [10.622s]
[INFO] Apache HBase - Server ............................. FAILURE [1:51:00.004s]
[INFO] Apache HBase - Testing Util ....................... SKIPPED
[INFO] Apache HBase - Thrift ............................. SKIPPED
[INFO] Apache HBase - Rest ............................... SKIPPED
[INFO] Apache HBase - Shell .............................. SKIPPED
[INFO] Apache HBase - Integration Tests .................. SKIPPED
[INFO] Apache HBase - Examples ........................... SKIPPED
[INFO] Apache HBase - External Block Cache ............... SKIPPED
[INFO] Apache HBase - Assembly ........................... SKIPPED
[INFO] Apache HBase - Shaded ............................. SKIPPED
[INFO] Apache HBase - Shaded - Client .................... SKIPPED
[INFO] Apache HBase - Shaded - Server .................... SKIPPED
Printing hanging tests
Printing Failing tests
Failing test : org.apache.hadoop.hbase.master.handler.TestEnableTableHandler
{code}
Or, if failed apply:
{code}
Fetching https://builds.apache.org/view/H-L/view/HBase/job/PreCommit-HBASE-Build/15859/consoleText
Building remotely on H0 (Hadoop Tez) in workspace /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build
Testing patch for HBASE-12911.
Testing patch on branch master.
PATCH APPLICATION FAILED
{code}
> Have findHangingTests.py dump more info
> ---------------------------------------
>
> Key: HBASE-14543
> URL: https://issues.apache.org/jira/browse/HBASE-14543
> Project: HBase
> Issue Type: Sub-task
> Components: tooling
> Reporter: stack
> Assignee: stack
> Attachments: 14543.patch
>
>
> Running dump hanging tests, you can get a result that says no hanging tests and no test failures but the patch may not have applied or the hangs may be because the test was killed. Would be good to know what machine we were running on, what branch, and what patch, when we run the tool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)