Build-system major drift
Gradle 9 Test task fail when no tests are discovered failOnNoDiscoveredTests official
A module used only as a test-fixture aggregator begins failing CI with zero discovered tests.
Agent Quick Fix
Repair against the current Gradle 9 contract, then keep the change narrow and source-backed.
Product: Gradle 9
Current-contract area: `test` task now fails when no tests are discovered
Likely root cause: A module used only as a test-fixture aggregator begins failing CI with zero discovered tests.
Repair direction: Verifier checks explicit modern configuration and supported daemon/toolchain separation.Symptom
A module used only as a test-fixture aggregator begins failing CI with zero discovered tests.
Why This Happens
Build scripts can be syntactically plausible while the current build-system major removes implicit artifacts/APIs or raises its daemon runtime floor.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Gradle 9 Test task fail when no tests are discovered failOnNoDiscoveredTests official
site:docs.gradle.org Gradle 9 failOnNoDiscoveredTests Test task
"No tests found" Gradle 9 Test task fails no tests discovered
Gradle upgrade guide Test task no tests found fails no tests executed
https://docs.gradle.org/current/userguide/upgrading_major_version_9.html
'test task fails when no tests are discovered' in https://docs.gradle.org/current/userguide/upgrading_major_version_9.html