accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3892) Problematic ITs
Date Thu, 26 May 2016 16:26:13 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Drob updated ACCUMULO-3892:
--------------------------------
    Fix Version/s:     (was: 1.7.2)
                   1.7.3

> Problematic ITs
> ---------------
>
>                 Key: ACCUMULO-3892
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3892
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.7.0
>            Reporter: Josh Elser
>            Priority: Minor
>             Fix For: 1.7.3, 1.8.0
>
>
> There are a few tests that I've regularly seem not want to pass during nightly automated
testing.
> {noformat}
> E AssertionError: test timed out after 300000 milliseconds
> E java.lang.Exception: test timed out after 300000 milliseconds
> E at java.lang.Thread.sleep(Native Method)
> E at org.apache.accumulo.core.util.UtilWaitThread.sleep(UtilWaitThread.java:27)
> E at org.apache.accumulo.core.client.impl.TableOperationsImpl.waitForTableStateTransition(TableOperationsImpl.java:1159)
> E at org.apache.accumulo.core.client.impl.TableOperationsImpl.online(TableOperationsImpl.java:1223)
> E at org.apache.accumulo.test.AssignmentThreadsIT.testConcurrentAssignmentPerformance(AssignmentThreadsIT.java:77)
> {noformat}
> {noformat}
> E AssertionError: test timed out after 90000 milliseconds
> E java.lang.Exception: test timed out after 90000 milliseconds
> E at sun.misc.Unsafe.park(Native Method)
> E at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> E at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1033)
> E at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
> E at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
> E at org.apache.accumulo.core.client.impl.TableOperationsImpl.addSplits(TableOperationsImpl.java:388)
> E at org.apache.accumulo.test.BalanceFasterIT.test(BalanceFasterIT.java:60)
> {noformat}
> {noformat}
> E AssertionError: test timed out after 360000 milliseconds
> E java.lang.Exception: test timed out after 360000 milliseconds
> E at java.lang.Object.wait(Native Method)
> E at java.lang.Thread.join(Thread.java:1281)
> E at java.lang.Thread.join(Thread.java:1355)
> E at org.apache.accumulo.test.InterruptibleScannersIT.test(InterruptibleScannersIT.java:98)
> {noformat}
> {noformat}
> E AssertionError: test timed out after 1440000 milliseconds
> E java.lang.Exception: test timed out after 1440000 milliseconds
> E at java.lang.Object.wait(Native Method)
> E at java.lang.Object.wait(Object.java:503)
> E at java.lang.UNIXProcess.waitFor(UNIXProcess.java:263)
> E at org.apache.accumulo.test.functional.MetadataMaxFilesIT.test(MetadataMaxFilesIT.java:84)
> {noformat}
> This is with a quadrupled timeout (if not 8x by now). I know these tests all _can_ pass
(as I ensured that doing 1.7.0 testing), but apparently something isn't good enough when running
on a EC2 m1.xlarges IIRC. I believe all of these tests are stretching the bounds on what is
really suitable for an integration test, IMO. Perhaps there is a better way to write the test
and verify the correctness that we want expect to see, but these tests are definitely not
reliably testing what we hope they are for me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message