[Task] No test-result publishing, ancient surefire, no flake retry
- Dominant language
- Java
- Stars
- 8.8k
- Forks
- 3.1k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 85
Description
## Description
No `dorny/test-reporter`, no `upload-artifact` of surefire-reports, no `rerunFailingTestsCount` anywhere. Surefire `3.0.0-M4` (a 2021 milestone) has known JUnit5 ordering bugs. No retry configured.
## Location
```
pom.xml:94 (maven-surefire-plugin.version 3.0.0-M4); no test-reporter/upload/retry in any workflow
```
## Impact
Hard triage; spurious red; surefire-version masking.
## Suggested fix
Add `dorny/test-reporter` + upload `**/surefire-reports/*.xml`; bump surefire to 3.2.5; set `rerunFailingTestsCount=1` for integration workflows.
## Related existing issue(s)
#6281 (flaky test task) is the symptom; this is the missing CI mechanism to handle it.
_Identified during the 2026-08-02 audit; full list in [`docs/issue-candidates-2026-08-02.md`](docs/issue-candidates-2026-08-02.md)._
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with pom.xml:94 and inspect the repository’s GitHub Actions workflow files for integration-test jobs. Check how surefire reports are produced and where test steps run. Done means the requested Surefire upgrade, retry setting, report publishing, and artifact upload are configured for the relevant workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100