java.lang.AssertionError: should have thrown IAE since we're requesting rollups while changing the Vec (got Vec.Writer)

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

,
Expert tip

Check your pattern declaration or check your assert declaration.

Solutions on the web

via JIRA by Brandon Hill, 1 year ago
should have thrown IAE since we're requesting rollups while changing the Vec (got Vec.Writer)
via JIRA by Brandon Hill, 1 year ago
should have thrown IAE since we're requesting rollups while changing the Vec (got Vec.Writer)
via Sonatype JIRA by Benjamin Hanzelmann, 1 year ago
No index .gz file should exist.
via GitHub by hasancelik
, 1 year ago
WriteBehind Queue was flushed too soon. Configured write delay: 2000 ms. But it took less than 30 ms to flush the queue.
via GitHub by hasancelik
, 1 year ago
WriteBehind Queue was flushed too soon. Configured write delay: 2000 ms. But it took less than 1 ms to flush the queue.
via GitHub by Donnerbart
, 1 year ago
No error should have been thrown, but ConsumeThread-2 completed error expected null, but was:<com.hazelcast.ringbuffer.StaleSequenceException: sequence:640700 is too small. The current headSequence is:640718 tailSequence is:641717>
java.lang.AssertionError: should have thrown IAE since we're requesting rollups while changing the Vec (got Vec.Writer)
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at water.fvec.FVecTest.testRollups(FVecTest.java:204)
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 water.TestUtil$2$TimerStatement.evaluate(TestUtil.java:95)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
at org.junit.runner.JUnitCore.run(JUnitCore.java:117)
at water.junit.H2OTestRunner.run(H2OTestRunner.java:44)
at water.junit.H2OTestRunner.main(H2OTestRunner.java:53)

Users with the same issue

4 times, 10 months ago
Once, 6 months ago
2 times, 11 months ago
2 times, 9 months ago
3 times, 6 months ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.