You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/13 07:32:46 UTC

[jira] [Created] (HBASE-14421) TestFastFail* are flakey

stack created HBASE-14421:
-----------------------------

             Summary: 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


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)