Description
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 <<< FAILURE! org.junit.ComparisonFailure: expected:<[123]> but was:<[456]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.accumulo.minicluster.MiniAccumuloClusterTest.test(MiniAccumuloClusterTest.java:133) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)