From e8eb8261e5762bc8ff03a6be44177f23da43f8be Mon Sep 17 00:00:00 2001 From: Brice Dutheil Date: Wed, 3 Jun 2026 10:50:57 +0200 Subject: [PATCH] Remove no-discovered-test override --- .../kotlin/dd-trace-java.configure-tests.gradle.kts | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/buildSrc/src/main/kotlin/dd-trace-java.configure-tests.gradle.kts b/buildSrc/src/main/kotlin/dd-trace-java.configure-tests.gradle.kts index 04862485528..ccd25ab6697 100644 --- a/buildSrc/src/main/kotlin/dd-trace-java.configure-tests.gradle.kts +++ b/buildSrc/src/main/kotlin/dd-trace-java.configure-tests.gradle.kts @@ -63,17 +63,6 @@ tasks.withType().configureEach { onlyIf("skipForkedTests are undefined or false") { !skipForkedTestsProvider.isPresent } } else { exclude("**/*ForkedTest*") - // Starting from Gradle 9.3, Gradle will fail if a test task has no discovered tests. - // While this can be a misconfiguration, dd-trace-java test suite conventions allow suites - // to contain abstract base classes that are extended by concrete forked test suites. - // - // Many instrumentation suites indeed only ship *ForkedTest concrete classes - // (the non-forked peer task created by `addTestSuiteExtendingForDir` exists only - // to host shared configurations/sources). Those test tasks won't have executable tests - // by design under the `**/*ForkedTest*` exclude rule above. So let's allow them. - // - // Related but not the issue here https://github.com/gradle/gradle/issues/36508 - failOnNoDiscoveredTests = false } // Set test timeout for 20 minutes. Default job timeout is 1h (configured on CI level).