slowness of implementation make some TCK tests to fail
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
BulkheadAsynchRetryTest#testBulkheadMethodAsynchronousRetry55Trip() fails because from time to time the 10 retries on the 11th failing service call can be served because of the first execution already ended.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running BulkheadAsynchRetryTest#testBulkheadMethodAsynchronousRetry55Trip() and inspect the asynchronous bulkhead and retry implementation involved in the test. Determine why the first execution can finish before all expected retries are served; done means the TCK test passes reliably without timing-dependent failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100