jgroups-extras / jgroups-extras/jgroups-aws
MockS3_PINGDiscoveryTestCase.testDiscovery is flaky in CI
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17
- Forks
- 12
- Avg merge
- 10d 15h
- Merged PRs (30d)
- 3
Description
MockS3_PINGDiscoveryTestCase.testDiscovery intermittently fails in CI with:
member count ==> expected: <5> but was: <4>
Fails non-deterministically on JDK 17 (Ubuntu/macOS); rerunning passes. Likely a timing issue on slower runners — the discovery timeout may need to be increased.
Example: https://github.com/jgroups-extras/jgroups-aws/actions/runs/25569466993/job/75061215084 (surfaced in #576)
Contributor guide
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 with MockS3_PINGDiscoveryTestCase.testDiscovery and the discovery timeout used by that test; inspect the intermittent JDK 17 CI failure and its timing assumptions. Done means the test reliably discovers all five members on the affected Ubuntu and macOS runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100