Transient failure in RemoteTaskRunnerTest.testStatusRemoved
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 31m
- Merged PRs (30d)
- 209
Description
```
Running org.apache.druid.indexing.overlord.RemoteTaskRunnerTest
Tests run: 23, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 55.974 sec <<< FAILURE! - in org.apache.druid.indexing.overlord.RemoteTaskRunnerTest
testStatusRemoved(org.apache.druid.indexing.overlord.RemoteTaskRunnerTest) Time elapsed: 21.19 sec <<< ERROR!
java.util.concurrent.TimeoutException: Timeout waiting for task.
at org.apache.druid.indexing.overlord.RemoteTaskRunnerTest.testStatusRemoved(RemoteTaskRunnerTest.java:315)
```
Contributor guide
Research direction
Start with RemoteTaskRunnerTest.testStatusRemoved, especially RemoteTaskRunnerTest.java:315, and run the test repeatedly to reproduce the timeout. Trace the wait that raises TimeoutException and identify why the test is transiently failing. Done means the test reliably completes without the timeout in the relevant test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100