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

Posted to notifications@accumulo.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/01/30 22:58:23 UTC

[jira] [Commented] (ACCUMULO-2295) Various ITs timing too sensitive

    [ https://issues.apache.org/jira/browse/ACCUMULO-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887133#comment-13887133 ] 

ASF subversion and git services commented on ACCUMULO-2295:
-----------------------------------------------------------

Commit 2611cba3bce0b3db3a7a61af405f9c2ac8ac97c1 in branch refs/heads/1.6.0-SNAPSHOT from [~vines]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=2611cba ]

ACCUMULO-2295 adjusting test timeouts


> 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
>             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)