Investigate several unit test failues with reuseForks set to true
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
With the work done in PR: #2007, unit tests now have reuseForks set to true by default. However, there are several tests that fail because of this. Those have been excluded and require further investigation on why they fail.
Current tests that fail below:
```
TableIdTest.java
HadoopCredentialProviderTest.java
IdleRatioScanPrioritizerTest.java
TestCfCqSlice.java
TestCfCqSliceSeekingFilter.java
AssignmentWatcherTest.java
AuthenticationTokenSecretManagerTest
```
EDIT: This list hasn't been updated so it's possible there are a couple more inside the pom.
Contributor guide
Research direction
Start by reproducing the unit-test failures introduced after PR #2007 and inspect the exclusions in the pom. Check TableIdTest.java, HadoopCredentialProviderTest.java, IdleRatioScanPrioritizerTest.java, TestCfCqSlice.java, TestCfCqSliceSeekingFilter.java, AssignmentWatcherTest.java, and AuthenticationTokenSecretManagerTest.java. Done means the affected tests pass with reuseForks enabled and the causes or any additional failures are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100