You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
StreamingEntryReaderTests is flaky. The testCanReadEntryFromMLedgerSizeExceededLimit test method fails sporadically.
It seems that the 300 millisecond timeout for async operations is too short.
example failure
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in
org.apache.pulsar.broker.service.streamingdispatch.StreamingEntryReaderTests that uses
java.util.concurrent.atomic.AtomicBoolean was not fulfilled within 300 milliseconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
at org.apache.pulsar.broker.service.streamingdispatch.StreamingEntryReaderTests.testCanReadEntryFromMLedgerSizeExceededLimit(StreamingEntryReaderTests.java:182)
Full exception stacktrace
[INFO] Running org.apache.pulsar.broker.service.streamingdispatch.StreamingEntryReaderTests
[ERROR] Tests run: 7, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 3.543 s <<< FAILURE! - in org.apache.pulsar.broker.service.streamingdispatch.StreamingEntryReaderTests
[ERROR] testCanReadEntryFromMLedgerSizeExceededLimit(org.apache.pulsar.broker.service.streamingdispatch.StreamingEntryReaderTests) Time elapsed: 0.346 s <<< FAILURE!
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in org.apache.pulsar.broker.service.streamingdispatch.StreamingEntryReaderTests that uses java.util.concurrent.atomic.AtomicBoolean was not fulfilled within 300 milliseconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
at org.apache.pulsar.broker.service.streamingdispatch.StreamingEntryReaderTests.testCanReadEntryFromMLedgerSizeExceededLimit(StreamingEntryReaderTests.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:45)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:73)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
The text was updated successfully, but these errors were encountered:
…der to reduce flakiness. (#9905)
Fixes#9885
### Motivation
StreamingEntryReaderTests is flaky. The testCanReadEntryFromMLedgerSizeExceededLimit test method fails sporadically.
### Modifications
Increased timeout to ease the bound.
fmiguelez
pushed a commit
to fmiguelez/pulsar
that referenced
this issue
Mar 16, 2021
…der to reduce flakiness. (apache#9905)
Fixesapache#9885
### Motivation
StreamingEntryReaderTests is flaky. The testCanReadEntryFromMLedgerSizeExceededLimit test method fails sporadically.
### Modifications
Increased timeout to ease the bound.
StreamingEntryReaderTests is flaky. The testCanReadEntryFromMLedgerSizeExceededLimit test method fails sporadically.
It seems that the 300 millisecond timeout for async operations is too short.
example failure
Full exception stacktrace
The text was updated successfully, but these errors were encountered: