[
https://issues.apache.org/jira/browse/HBASE-14427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993543#comment-14993543
]
Abhishek Singh Chouhan commented on HBASE-14427:
------------------------------------------------
Since the fix already went in
(https://github.com/apache/hbase/commit/b3afdb8de1a9fa88c553159b2d2d2aa96902a345)
, only pushing the addendum to reenable it should do i guess. If a patch
adds/re-enables a test, does the QA run the added tests also for the same
patch? If yes then we can probably get QA runs and see how the test is faring.
> Fix 'should' assertions in TestFastFail
> ---------------------------------------
>
> Key: HBASE-14427
> URL: https://issues.apache.org/jira/browse/HBASE-14427
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: Abhishek Singh Chouhan
> Priority: Minor
> Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-14427.addendum.patch, HBASE-14427.patch
>
>
> Over in HBASE-14421, TestFastFail has been failing assertions that talk of
> events that 'should' be happening. Fix. For now HBASE-14421 has disabled the
> 'should' assertions. They seem fine on apache jenkins build but fail fairly
> reliably for me on alternate HW.
> To address, get familiar with the test. Change the commented out asserts to
> be yes/no instead of a 'likely' (On a cursory scan, it is possible that a
> test run may not involve preemption and it is these runs that are throwing
> asserts).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
