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-14421) TestFastFail* are flakey
Date Fri, 25 Sep 2015 00:56:04 GMT

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

Hudson commented on HBASE-14421:
--------------------------------

FAILURE: Integrated in HBase-TRUNK #6837 (See [https://builds.apache.org/job/HBase-TRUNK/6837/])
HBASE-14421 Follow-on from HBASE-14421, just disable TestFastFail* until someone digs in and
fixes it (stack: rev d1405322f03eb70c7bb3d5a75810c551b343e60e)
* hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFastFail.java
HBASE-14421 Follow-on from HBASE-14421, just disable TestFastFail* until someone digs in and
fixes it; ADDENDUM -- missing import (stack: rev 9557bc7dfa3a48b668dda379a25eeaba41d33356)
* hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFastFail.java


> TestFastFail* are flakey
> ------------------------
>
>                 Key: HBASE-14421
>                 URL: https://issues.apache.org/jira/browse/HBASE-14421
>             Project: HBase
>          Issue Type: Sub-task
>          Components: test
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: 14421.addendum.txt, 14421.second.addendum.txt, 14421.third.addendum.txt,
14421.txt
>
>
> Running master test suite on a cluster, too often rig stops with a TestFastFail#testFastFail
failure with 'There *should* be at least one Premptive exception...' (emphasis mine). 'should'
seems too weak a basis for an assertion. Disable (there are plenty of other assertions on
how TestFastFail runs at end of test for it still to be valuable). I also see TestFastFailWithoutTestUtil
failing in testPreemptiveFastFailException. Here there is an issue with the latching that
needs looking into. For now, rather than fail the test, just dump out a thread dump. Someone
can spend time on it later. Meantime, stop it preventing test rig running.
> Also add in a timeout on the TestHCM class... I see this one stuck hanging out ... as
a zombie inside a test. A timeout might convert this to a test fail. Trying.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message