Reuse source sets for forked test tasks

[AlexeyKuznetsov-DD]

What Does This Do

Replaces ten duplicate forked-test source sets across eight instrumentation modules with addForkedTestTask(...).

The affected tasks now reuse their parent source set's compiled output and runtime classpath instead of recompiling identical sources. This also removes redundant forked compile-task configuration, preserves the latest-dependency test flag for the new task name, and updates the Gradle guide.

The migrated modules cover Akka actor and HTTP, AWS SDK 1.x and 2.x, Spring scheduling and Web MVC, Tomcat, and Vert.x Web.

Motivation

#12147 introduces addForkedTestTask for running a custom source set's *ForkedTest classes in isolated JVMs.

These modules currently create a second source set with the same sources and dependencies solely to obtain a forked runner. Reusing the original source set removes duplicate configurations and compilation while preserving test isolation and CI task selection.

This PR is stacked on #12147.

Additional Notes

Task names now follow the helper's <sourceSetName>ForkedTest convention; for example, latestDepForkedTest becomes latestDepTestForkedTest because it runs the latestDepTest source set.

Validation:

• All ten migrated forked tasks ran with fresh outputs: 1,000 test cases, 0 failures, 275 conditional skips.
• The four latest-dependency tasks ran after applying their required test flag: 643 test cases, 0 failures, 153 conditional skips.
• ./gradlew spotlessGroovyGradleCheck passed.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[datadog-prod-us1-6]

More details

The migrated tasks keep their source-set output, runtime classpath, forked-test filters, JVM limits, and latest-dependency flag behavior.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 37f08f6 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[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.83 s	14.68 s	[+0.1%; +2.0%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.58 s	13.70 s	[-1.4%; -0.3%] (maybe better)
startup:petclinic:appsec:Agent	17.61 s	17.27 s	[+1.2%; +2.8%] (significantly worse)
startup:petclinic:iast:Agent	17.24 s	17.52 s	[-2.3%; -0.9%] (maybe better)
startup:petclinic:profiling:Agent	17.19 s	17.39 s	[-2.4%; +0.1%] (no difference)
startup:petclinic:sca:Agent	17.47 s	17.42 s	[-0.7%; +1.3%] (no difference)
startup:petclinic:tracing:Agent	16.56 s	16.61 s	[-1.3%; +0.8%] (no difference)

Commit: 3a289777 · 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]

Thanks for the refactor.

[AlexeyKuznetsov-DD]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-04 21:49:00 UTC ℹ️ Start processing command /merge

---

2026-09-04 21:49:05 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-09-04 22:51:15 UTC ℹ️ MergeQueue: This merge request was merged