Skip to content

Fix testWithJava21 task running zero tests#4227

Merged
andimarek merged 1 commit intomasterfrom
fix-testWithJava21-no-tests
Jan 26, 2026
Merged

Fix testWithJava21 task running zero tests#4227
andimarek merged 1 commit intomasterfrom
fix-testWithJava21-no-tests

Conversation

@andimarek
Copy link
Member

@andimarek andimarek commented Jan 26, 2026

Summary

  • The testWithJava21 Gradle task was missing testClassesDirs, classpath, and dependsOn configuration, causing it to discover zero test classes and silently succeed with 0 tests executed
  • CI logs confirm: testWithJava21 completed in ~2 minutes with "0 tests run in 0 ms" while testWithJava17 and testWithJava11 each ran 5336 tests in ~7 minutes
  • Added the same configuration that testWithJava17 and testWithJava11 already have

Test plan

  • Verify the testWithJava21 CI job now reports 5336 tests (matching Java 11 and Java 17)
  • Verify the testWithJava21 CI job duration is ~7 minutes (matching Java 11 and Java 17), no longer ~2 minutes
  • Verify all other CI matrix jobs still pass

🤖 Generated with Claude Code

@andimarek @claude
Fix testWithJava21 task running zero tests
1af424c 
The testWithJava21 task was missing testClassesDirs, classpath, and
dependsOn configuration that testWithJava17 and testWithJava11 have.
Without these, Gradle finds no test classes and silently succeeds
with 0 tests executed.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@github-actions
Copy link
Contributor

github-actions bot commented Jan 26, 2026 •
edited
Loading

Test Results

  327 files  ±0    327 suites  ±0   5m 7s ⏱️ -8s
5 248 tests ±0  5 239 ✅  - 1  9 💤 +1  0 ❌ ±0 
5 337 runs  ±0  5 328 ✅  - 1  9 💤 +1  0 ❌ ±0 

Results for commit 1af424c. ± Comparison against base commit 6c2cdb0.

This pull request removes 196 and adds 172 tests. Note that renamed tests count towards both. 
	?

	, expected: combo-\"\\\b\f\n\r\t, #4]
                __schema { types { fields { args { type { name fields { name }}}}}}
                __schema { types { fields { type { name fields { name }}}}}
                __schema { types { inputFields { type { inputFields { name }}}}}
                __schema { types { interfaces { fields { type { interfaces { name } } } } } }
                __schema { types { name} }
                __type(name : "t") { name }
                a1: __schema { types { name} }
                a1: __type(name : "t") { name }
…

graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure23@43e9089 delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure24@3c5dbdf8 delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure25@352c44a8 delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure20@60bbacfc delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure21@65b97f47 delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure22@255eaa6b delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure3@44e93c1f delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure4@7efd28bd delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure5@472a11ae delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertNotNull with different number of error args with non null does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_6prov0_closure6@644ded04 delegate=graphql.AssertTest@9b21bd3 owner=graphql.AssertTest@9b21bd3 thisObject=graphql.AssertTest@9b21bd3 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
…
This pull request skips 1 test. 
graphql.schema.fetching.LambdaFetchingSupportTest ‑ different class loaders induce certain behaviours

♻️ This comment has been updated with latest results.

@andimarek andimarek merged commit f1c521c into master Jan 26, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@andimarek