question-mark
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: PersistentStreamingDispatcherBlockConsumerTest. testBlockBrokerDispatching

See original GitHub issue

PersistentStreamingDispatcherBlockConsumerTest is flaky. The testBlockBrokerDispatching test method fails sporadically.

example failure

  Error:  testBlockBrokerDispatching(org.apache.pulsar.broker.service.persistent.PersistentStreamingDispatcherBlockConsumerTest)  Time elapsed: 10.142 s  <<< FAILURE!
1148
  org.testng.internal.thread.ThreadTimeoutException: Method org.apache.pulsar.client.api.DispatcherBlockConsumerTest.testBlockBrokerDispatching() didn't finish within the time-out 10000
Full exception stacktrace
Error:  testBlockBrokerDispatching(org.apache.pulsar.broker.service.persistent.PersistentStreamingDispatcherBlockConsumerTest)  Time elapsed: 10.142 s  <<< FAILURE!
1148
  org.testng.internal.thread.ThreadTimeoutException: Method org.apache.pulsar.client.api.DispatcherBlockConsumerTest.testBlockBrokerDispatching() didn't finish within the time-out 10000
1149
  	at org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:371)
1150
  	at org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:282)
1151
  	at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:605)
1152
  	at org.testng.internal.TestInvoker.retryFailed(TestInvoker.java:214)
1153
  	at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:58)
1154
  	at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:822)
1155
  	at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:147)
1156
  	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
1157
  	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
1158
  	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
1159
  	at org.testng.TestRunner.privateRun(TestRunner.java:764)
1160
  	at org.testng.TestRunner.run(TestRunner.java:585)
1161
  	at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
1162
  	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
1163
  	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
1164
  	at org.testng.SuiteRunner.run(SuiteRunner.java:286)
1165
  	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
1166
  	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
1167
  	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1218)
1168
  	at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
1169
  	at org.testng.TestNG.runSuites(TestNG.java:1069)
1170
  	at org.testng.TestNG.run(TestNG.java:1037)
1171
  	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
1172
  	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
1173
  	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeLazy(TestNGDirectoryTestSuite.java:123)
1174
  	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:90)
1175
  	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
1176
  	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
1177
  	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
1178
  	at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
1179
  	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
Jason918commented, Nov 23, 2021

Checked with the code, I think it’s most likely because of the receive timeout setting is too small in line 821, it should use receive()

@Jason918 good catch! Could it fix the various failures listed in my previous comment?

OK,I will look into these.

0reactions
lhotaricommented, Nov 23, 2021

Checked with the code, I think it’s most likely because of the receive timeout setting is too small in line 821, it should use receive()

@Jason918 good catch! Could it fix the various failures listed in my previous comment?

Read more comments on GitHub >

github_iconTop Results From Across the Web

[Issue 12883] Fix flaky test in ...
A quick fix for flaky test in PersistentStreamingDispatcherBlockConsumerTest. The reason of time increase is most likely the warning logs in metadata store.
Read more >
Apache Pulsar 2.9.2
... by message receive timeout in testBlockBrokerDispatching #12954; Fix flaky test in PersistentStreamingDispatcherBlockConsumerTest #12943 ...
Read more >
apache/pulsar v2.9.2 on GitHub - NewReleases.io
... by message receive timeout in testBlockBrokerDispatching #12954; [issue 12883] Fix flaky test in PersistentStreamingDispatcherBlockConsumerTest #12943 ...
Read more >
Unnecessary collection nesting? - Laravel/Jetstream - IssueHint
Unnecessary collection nesting? This issue has been created since 2021-07-07. Since the raw query builder is used ...
Read more >
Add default NetworkPolicies - Keycloak/Keycloak-Operator - IssueHint
This issue has been created since 2022-02-18. Description. Add a sensible default NetworkPolicies for the operator to be able to connect with the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found