accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-2025) MiniAccumuloClusterTest failure
Date Mon, 16 Dec 2013 17:39:06 GMT
Josh Elser created ACCUMULO-2025:

             Summary: MiniAccumuloClusterTest failure
                 Key: ACCUMULO-2025
             Project: Accumulo
          Issue Type: Bug
          Components: mini
            Reporter: Josh Elser
             Fix For: 1.6.0

The only way I can see this happening is that both Mutations got the same timestamp at which
point the ordering should be arbitrary which means that the CRC=456 was added after the CRC=123.
But, even so, this seems to not be adhering to the contract of BatchWriter.flush().

Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.85 sec <<< FAILURE!
test(org.apache.accumulo.minicluster.MiniAccumuloClusterTest)  Time elapsed: 0.498 sec  <<<
org.junit.ComparisonFailure: expected:<[123]> but was:<[456]>
	at org.junit.Assert.assertEquals(
	at org.junit.Assert.assertEquals(
	at org.apache.accumulo.minicluster.MiniAccumuloClusterTest.test(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(
	at org.junit.internal.runners.statements.FailOnTimeout$

This message was sent by Atlassian JIRA

View raw message