[codex] Remove no-discovered-test override

[bric3]

What changed

Removes the failOnNoDiscoveredTests = false override from the shared Gradle test-task convention.

Why

This is an experiment after #11538 restored explicit testClassesDirs/classpath wiring for custom Test tasks. CI should show whether the no-discovered-tests override is still required after the custom task wiring fix.

Validation

• ./gradlew :buildSrc:compileKotlin

[datadog-datadog-prod-us1-2]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 41 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-java | test_inst: [11, 1/8]

See error

Test task did not discover any tests to execute due to likely misconfiguration.

DataDog/apm-reliability/dd-trace-java | test_inst: [11, 8/8]

See error

Test task did not discover any tests to execute due to misconfiguration in test sources.

DataDog/apm-reliability/dd-trace-java | test_inst: [17, 1/8]

See error

4 test tasks failed to execute due to misconfiguration: tests were not discovered.

View all 41 failed jobs.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: e8eb826 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.10 s	13.96 s	[-0.2%; +2.2%] (no difference)
startup:insecure-bank:tracing:Agent	12.94 s	13.03 s	[-1.7%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	16.46 s	15.54 s	[-3.1%; +14.9%] (unstable)
startup:petclinic:iast:Agent	16.40 s	16.51 s	[-2.3%; +0.9%] (no difference)
startup:petclinic:profiling:Agent	16.41 s	16.60 s	[-2.9%; +0.6%] (no difference)
startup:petclinic:tracing:Agent	15.86 s	14.99 s	[-3.0%; +14.6%] (unstable)

Commit:e8eb8261 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[bric3]

Wrong direction