[
https://issues.apache.org/jira/browse/HBASE-14421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744218#comment-14744218
]
Hudson commented on HBASE-14421:
--------------------------------
FAILURE: Integrated in HBase-1.3 #171 (See
[https://builds.apache.org/job/HBase-1.3/171/])
HBASE-14421 TestFastFail* are flakey; ADDENDUM 3 Exclude another should assert
in TestFastFail (stack: rev 233c1ee875a2068111e7ba7493e30676226bac90)
* 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)
