Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Flaky-test: DeadLetterTopicTest.testDeadLetterTopic

See original GitHub issue

Flaky-test: org.apache.pulsar.client.api.DeadLetterTopicTest.testDeadLetterTopic Number of failures: 20

org.apache.pulsar.client.api.DeadLetterTopicTest is flaky. The testDeadLetterTopic test method fails sporadically.

java.lang.AssertionError: expected [null] but found [org.apache.pulsar.client.impl.MessageImpl@151b99cf]
	at org.testng.Assert.fail(Assert.java:99)
	at org.testng.Assert.failNotSame(Assert.java:1033)
	at org.testng.Assert.assertNull(Assert.java:965)
	at org.testng.Assert.assertNull(Assert.java:953)
	at org.apache.pulsar.client.api.DeadLetterTopicTest.testDeadLetterTopic(DeadLetterTopicTest.java:124)

Full exception stacktrace

java.lang.AssertionError: expected [null] but found [org.apache.pulsar.client.impl.MessageImpl@151b99cf]
	at org.testng.Assert.fail(Assert.java:99)
	at org.testng.Assert.failNotSame(Assert.java:1033)
	at org.testng.Assert.assertNull(Assert.java:965)
	at org.testng.Assert.assertNull(Assert.java:953)
	at org.apache.pulsar.client.api.DeadLetterTopicTest.testDeadLetterTopic(DeadLetterTopicTest.java:124)
	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)

Flaky-test: org.apache.pulsar.client.api.DeadLetterTopicTest.testDeadLetterTopicByCustomTopicName Number of failures: 8

org.apache.pulsar.client.api.DeadLetterTopicTest is flaky. The testDeadLetterTopicByCustomTopicName test method fails sporadically.

java.lang.AssertionError: expected [null] but found [org.apache.pulsar.client.impl.MessageImpl@4490d295]
	at org.testng.Assert.fail(Assert.java:99)
	at org.testng.Assert.failNotSame(Assert.java:1033)
	at org.testng.Assert.assertNull(Assert.java:965)
	at org.testng.Assert.assertNull(Assert.java:953)
	at org.apache.pulsar.client.api.DeadLetterTopicTest.testDeadLetterTopicByCustomTopicName(DeadLetterTopicTest.java:397)

Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click. example failure 2021-03-08T00:50:56.6220381Z example failure 2021-03-06T02:41:58.7663850Z example failure 2021-03-16T00:25:57.4946126Z example failure 2021-03-15T15:47:58.3723431Z example failure 2021-02-26T21:53:13.5461069Z example failure 2021-03-11T17:33:24.1271868Z example failure 2021-03-09T02:10:02.8676980Z example failure 2021-03-10T17:22:30.4745269Z

Full exception stacktrace

java.lang.AssertionError: expected [null] but found [org.apache.pulsar.client.impl.MessageImpl@4490d295]
	at org.testng.Assert.fail(Assert.java:99)
	at org.testng.Assert.failNotSame(Assert.java:1033)
	at org.testng.Assert.assertNull(Assert.java:965)
	at org.testng.Assert.assertNull(Assert.java:953)
	at org.apache.pulsar.client.api.DeadLetterTopicTest.testDeadLetterTopicByCustomTopicName(DeadLetterTopicTest.java:397)
	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)

Issue Analytics

State:
Created 3 years ago
Comments:16 (16 by maintainers)

Top GitHub Comments

1reaction

michaeljmarshallcommented, Mar 19, 2021

Quick note: it does seem rather intentional that we send to the DLQ first and only acknowledge the message on the original topic upon successful delivery to the DLQ. This ordering is essential to our DLQ delivery semantics. If we switched the order, we’d end up with an at most once delivery to the DLQ, which seems undesirable to me and like a breaking change from the current behavior.

I have a few potential solutions that I need to spend a little more time thinking through. I’ll post an update tomorrow.

0reactions

tisonkuncommented, Dec 11, 2022

Closed as stale. Please create a new issue if it’s still relevant to the maintained versions.

Top Results From Across the Web

[GitHub] [pulsar] codelipenghui commented on issue #9916: Flaky ...

[GitHub] [pulsar] codelipenghui commented on issue #9916: Flaky-test: DeadLetterTopicTest.testDeadLetterTopic · Previous message · View by thread · View by date ...