accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-2563) simple.merge.MergeTest fails
Date Tue, 10 Jun 2014 14:38:03 GMT

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

Josh Elser resolved ACCUMULO-2563.
----------------------------------

    Resolution: Won't Fix

> simple.merge.MergeTest fails
> ----------------------------
>
>                 Key: ACCUMULO-2563
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2563
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.4.5
>            Reporter: Josh Elser
>            Priority: Minor
>              Labels: needs_verification
>
> Reliably seeing failure of this test on an early Hadoop 2.4.0
> {noformat}
> 00:08:07 runTest (simple.merge.MergeTest) ................................... ERROR:test.auto:This
looks like a stack trace: Thread "org.apache.accumulo.server.test.functional.FunctionalTest"
died split inconsistency foo6_3 [m, b, r] != [r]
> java.lang.Exception: split inconsistency foo6_3 [m, b, r] != [r]
> 	at org.apache.accumulo.server.test.functional.MergeTest.runMergeTest(MergeTest.java:135)
> 	at org.apache.accumulo.server.test.functional.MergeTest.runMergeTest(MergeTest.java:85)
> 	at org.apache.accumulo.server.test.functional.MergeTest.run(MergeTest.java:69)
> 	at org.apache.accumulo.server.test.functional.FunctionalTest.main(FunctionalTest.java:312)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.apache.accumulo.start.Main$1.run(Main.java:92)
> 	at java.lang.Thread.run(Thread.java:744)
> {noformat}
> The actual failure message is variant across different failure runs ({{foo6_3 \[m, b,
r\] != \[r\]}}, {{foo8_0 \[m, b, r\] != \[m, b\]}}, {{foo7_0 \[m, b, r\] != \[b\]}}, etc),
but it has failed for me at least 5 times in a row.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message