NationalSecurityAgency / NationalSecurityAgency/datawave
SharedCacheCoordinatorTest is flaky
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 735
- Forks
- 294
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 25
Description
Occasionally SharedCacheCoordinatorTest fails with the following message after building with mvn clean install:
SharedCacheCoordinatorTest.testSharedCounterUpdateAfterReconnect:123 Client never reconnected. expected:<RECONNECTED> but was:<SUSPENDED>
This will usually pass again after rebuilding once or twice.
Full surefire report here:
datawave.webservice.common.cache.SharedCacheCoordinatorTest-output.txt
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 with datawave.webservice.common.cache.SharedCacheCoordinatorTest, especially testSharedCounterUpdateAfterReconnect at line 123, and reproduce the failure with mvn clean install. Review the linked surefire report for the SUSPENDED versus RECONNECTED sequence; done means the test reliably observes reconnection after a clean build.
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
- Mostly clear
- Newbie friendliness
- 38/100