[
https://issues.apache.org/jira/browse/ACCUMULO-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093592#comment-16093592
]
Michael Miller commented on ACCUMULO-4602:
------------------------------------------
The issues still exist with AssignmentThreadsIT (and most likely DurabilityIT
as well). I looked at AssignmentThreadsIT and made some minor improvements but
the test still has fundamental timing issues. It is measuring the time it
takes to bring a table online, once with 1 max assignment thread and again with
20 max. Although, it passes most of the time, I don't think adjusting this
property has much influence on the time measured. For instance, I put a debug
statements in TabletServerResourceManager SimpleTimer that checks for a change
in the Max pool size property. I could see the "tablet assignment" thread pool
corePoolSize change from 1 -> 20 but the poolSize remains 1 for the entire
test. I think this test should just be removed.
> Assorted flakey ITs that appear to be timeout sensitive
> -------------------------------------------------------
>
> Key: ACCUMULO-4602
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4602
> Project: Accumulo
> Issue Type: Bug
> Components: test
> Affects Versions: 1.7.3
> Reporter: Josh Elser
> Priority: Minor
> Fix For: 1.7.4, 1.8.2, 2.0.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {noformat}
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 48.387 sec
> <<< FAILURE! - in org.apache.accumulo.test.AssignmentThreadsIT
> testConcurrentAssignmentPerformance(org.apache.accumulo.test.AssignmentThreadsIT)
> Time elapsed: 48.266 sec <<< FAILURE!
> java.lang.AssertionError
> at
> org.apache.accumulo.test.AssignmentThreadsIT.testConcurrentAssignmentPerformance(AssignmentThreadsIT.java:91)
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 60.177 sec
> <<< FAILURE! - in org.apache.accumulo.test.BadDeleteMarkersCreatedIT
> test(org.apache.accumulo.test.BadDeleteMarkersCreatedIT) Time elapsed:
> 60.011 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 60 seconds
> {noformat}
> Both of these appear to just be sensitive to timings, and, as such, should
> not be tests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
