Fix Gradle custom test task wiring

[AlexeyKuznetsov-DD]

What Does This Do

Wires custom Test tasks explicitly to their intended source set outputs:

• shared forkedTest -> sourceSets.test
• shared testRuntimeActivation -> sourceSets.test
• Scala cross-version tasks -> regular test classes plus version-specific Scala support classes

Motivation

After moving to Gradle 9.5.1, these custom Test tasks no longer inherited the implicit test source set wiring that made them run under Gradle 8.14.4; without explicit testClassesDirs/classpath, they were skipped as NO-SOURCE.

Additional Notes

Checked custom Test task wiring across the repo. The only remaining empty task is the parent :dd-java-agent:instrumentation:latestDepTest placeholder.

Follow up to

• Bump to Gradle 9.5.1 #11436

[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.84 s	14.68 s	[-0.5%; +2.7%] (no difference)
startup:insecure-bank:tracing:Agent	13.69 s	13.74 s	[-1.8%; +1.1%] (no difference)
startup:petclinic:appsec:Agent	16.66 s	16.39 s	[+0.0%; +3.2%] (maybe worse)
startup:petclinic:iast:Agent	16.54 s	16.57 s	[-1.5%; +1.1%] (no difference)
startup:petclinic:profiling:Agent	16.40 s	16.50 s	[-2.0%; +0.8%] (no difference)
startup:petclinic:tracing:Agent	14.96 s	16.14 s	[-15.3%; +0.8%] (unstable)

Commit:87c8630a · 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.

[AlexeyKuznetsov-DD]

@bric3 Feel free to refactor this PR if needed.

[bric3]

The issue appear to be related to a convention that has been removed in Gradle 9.x

https://docs.gradle.org/current/userguide/upgrading_major_version_9.html#test_tasks_may_no_longer_execute_expected_tests

[bric3]

/merge -f --reason="Fixes NO SOURCES, merge queue not needed"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-03 08:42:56 UTC ℹ️ Start processing command /merge -f --reason="Fixes NO SOURCES, merge queue not needed"

---

2026-06-03 08:43:00 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-06-03 08:43:10 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: Fixes NO SOURCES, merge queue not needed