devinbost commented on issue #9916: URL: https://github.com/apache/pulsar/issues/9916#issuecomment-814607672
I didn't see anything really useful in the logs, but perhaps this stack trace will be of some value. Errors: 0, Skipped: 2, Time elapsed: 66.568 s <<< FAILURE! - in org.apache.pulsar.client.api.DeadLetterTopicTest 233Error: testDeadLetterTopic(org.apache.pulsar.client.api.DeadLetterTopicTest) Time elapsed: 6.148 s <<< FAILURE! 234java.lang.AssertionError: expected [null] but found ***@***.*** 235 at org.testng.Assert.fail(Assert.java:99) 236 at org.testng.Assert.failNotSame(Assert.java:1033) 237 at org.testng.Assert.assertNull(Assert.java:965) 238 at org.testng.Assert.assertNull(Assert.java:953) 239 at org.apache.pulsar.client.api.DeadLetterTopicTest.testDeadLetterTopic(DeadLetterTopicTest.java:125) 240 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 241 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 242 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 243 at java.lang.reflect.Method.invoke(Method.java:498) 244 at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132) 245 at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:45) 246 at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:73) 247 at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11) 248 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 249 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 250 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 251 at java.lang.Thread.run(Thread.java:748) 252 -- Devin G. Bost On Tue, Apr 6, 2021, 10:59 PM Michael Marshall ***@***.***> wrote: > @devinbost <https://github.com/devinbost> - I agree that those conditions > make these tests more likely to fail. This test is also problematic because > the underlying dead letter logic has a data race that can lead to messages > being read from both the DLQ topic and then from the source topic. Any > chance that you looked up the logs before triggering another run of that > test? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/pulsar/issues/9916#issuecomment-814601113>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABYTBL3E4HZDD6UC2MQQYTTTHPREXANCNFSM4ZINSFLQ> > . > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
