[
https://issues.apache.org/jira/browse/ACCUMULO-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888130#comment-13888130
]
John Vines commented on ACCUMULO-2295:
--------------------------------------
I don't think that's feasible for junit's timeout test. I could be wrong, I've
done 0 research.
At the very least, that would be more applicable if the current timing settings
for all the tests were in the same realm of accuracy, which is what I'm really
trying to deal with right now.
> Various ITs timing too sensitive
> --------------------------------
>
> Key: ACCUMULO-2295
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2295
> Project: Accumulo
> Issue Type: Bug
> Components: test
> Reporter: John Vines
> Assignee: John Vines
> Fix For: 1.6.0
>
>
> There are several ITs which have such tight timing that they routinely fail
> with multiple test threads but run perfectly fine when run solo. Some of
> these include-
> # ConfigurableMajorCompactionIT.java
> # BatchWriterFlushIT.java
> # BulkSplitOptimizationIT.java
> # ReadWriteIT.java
> # SslIT.java
> # StartIT.java
> # TimeoutIT.java
> # WriteLotsIT.java
> There are some others which time out, but they already have a large timeout
> so I'm a bit weary to chalk them up to their timing being too tight.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
