Failure Details
Failed Jobs
| Job |
Status |
| buildAndTest (assemble && ./gradlew check, check) |
failure |
| buildAndTest (testWithJava17 testngWithJava17, java17, ...) |
cancelled |
| buildAndTest (test testng jacocoTestReport, java25, ...) |
cancelled |
| buildAndTest (testWithJava21 testngWithJava21, java21, ...) |
cancelled |
| buildAndTest (testWithJava11 testngWithJava11, java11, ...) |
cancelled |
| allBuildAndTestSuccessful |
failure (dependent) |
The check job's "build and test" step failed after ~7 minutes (00:08:14 → 00:15:37), causing all other jobs to be cancelled.
Root Cause
PR #4330 made two related changes that together expose a behaviour difference:
In build.gradle (removed lines):
check.dependsOn testng // removed
test.dependsOn testWithJava21 // removed
test.dependsOn testWithJava17 // removed
test.dependsOn testWithJava11 // removed
In .github/workflows/pull_request.yml (changed check matrix entry):
- gradle-argument: 'assemble && ./gradlew check -x test -x testng -x testngWithJava11 -x testngWithJava17 -x testngWithJava21'
+ gradle-argument: 'assemble && ./gradlew check'
The problem: The -x test exclusion was removed from the check CI job without accounting for the fact that the standard Gradle Java plugin always makes check depend on test. Removing check.dependsOn testng is correct (testng no longer needs to be in check), but removing -x test from the CI check job means the full JUnit test suite now runs during check — which was not the intent of that matrix entry. The check job was designed to run only lint/compile/style verifications (NullAway, ErrorProne, etc.), while a dedicated java25 matrix entry runs the tests separately.
The ~7-minute duration of the failure is consistent with the full test suite running before encountering a failure (or possibly a flaky test surfacing).
Recommended Fix
Restore the -x test exclusion in the check matrix entry while keeping the -x testng exclusion removed (since check.dependsOn testng was correctly removed):
.github/workflows/pull_request.yml and .github/workflows/master.yml:
- gradle-argument: 'assemble && ./gradlew check'
+ gradle-argument: 'assemble && ./gradlew check -x test'
This preserves the intent of the PR (simplifying test task dependencies) while keeping the check job focused on non-test verification tasks. The java25 matrix entry correctly handles running test testng jacocoTestReport separately.
Alternatively, if the intent is to also run tests in the check job, investigate and fix any failing tests by inspecting the full job logs at the run URL above.
Generated by CI Failure Doctor · ◷
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/ci-doctor.md@ee50a3b7d1d3eb4a8c409ac9409fd61c9a66b0f5
Failure Details
Failed Jobs
The check job's "build and test" step failed after ~7 minutes (00:08:14 → 00:15:37), causing all other jobs to be cancelled.
Root Cause
PR #4330 made two related changes that together expose a behaviour difference:
In build.gradle (removed lines):
In .github/workflows/pull_request.yml (changed check matrix entry):
The problem: The -x test exclusion was removed from the check CI job without accounting for the fact that the standard Gradle Java plugin always makes check depend on test. Removing check.dependsOn testng is correct (testng no longer needs to be in check), but removing -x test from the CI check job means the full JUnit test suite now runs during check — which was not the intent of that matrix entry. The check job was designed to run only lint/compile/style verifications (NullAway, ErrorProne, etc.), while a dedicated java25 matrix entry runs the tests separately.
The ~7-minute duration of the failure is consistent with the full test suite running before encountering a failure (or possibly a flaky test surfacing).
Recommended Fix
Restore the -x test exclusion in the check matrix entry while keeping the -x testng exclusion removed (since check.dependsOn testng was correctly removed):
.github/workflows/pull_request.yml and .github/workflows/master.yml:
This preserves the intent of the PR (simplifying test task dependencies) while keeping the check job focused on non-test verification tasks. The java25 matrix entry correctly handles running test testng jacocoTestReport separately.
Alternatively, if the intent is to also run tests in the check job, investigate and fix any failing tests by inspecting the full job logs at the run URL above.