paul-rogers opened a new issue, #12866: URL: https://github.com/apache/druid/issues/12866
The UT `RemoteTaskRunnerTest.testRunPendingTaskFailToAssignTask` failed in [this build](https://app.travis-ci.com/github/apache/druid/jobs/578832603): ```text [ERROR] Tests run: 29, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 72.402 s <<< FAILURE! - in org.apache.druid.indexing.overlord.RemoteTaskRunnerTest [ERROR] org.apache.druid.indexing.overlord.RemoteTaskRunnerTest.testRunPendingTaskFailToAssignTask Time elapsed: 0.271 s <<< ERROR! java.util.concurrent.TimeoutException: Timeout waiting for task. at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:269) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:96) at org.apache.druid.indexing.overlord.RemoteTaskRunnerTest.testRunPendingTaskFailToAssignTask(RemoteTaskRunnerTest.java:576) ``` It is evidently known that this test is flaky: ```java // higher timeout to reduce flakiness on CI pipeline ``` The same test passes when run on a Mac in the IDE. The test passed in earlier builds on Travis in this branch. The branch in question changed only SQL classes, but nothing in the Overlord. Conclusion: flaky test. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
