Enable Pekko HTTP forked tests

[AlexeyKuznetsov-DD]

What Does This Do

Enables the six existing Pekko HTTP *ForkedTest classes across the base, latest Pekko 1.0.x, and latest dependency test suites.

It also fixes the failures exposed by that coverage:

• skips context injection when singleRequest receives a null request;
• verifies the null-carrier path directly; and
• updates the exception-span assertions for schema-specific operation names and absent peer metadata.

Motivation

Pekko's tests live in custom source sets, so the default forkedTest task used the empty test source set. The six forked classes were compiled but never executed.

Enabling them exposed a suppressed Data Streams injection failure when the existing exception test calls singleRequest(null):

java.lang.NullPointerException: Cannot invoke "HttpRequest.addHeader(...)" because "this.request" is null
    at PekkoHttpClientHelpers$PekkoHttpHeaders.set(...)
    at DataStreamsPropagator.injectPathwayContext(...)

The context-propagation advice now returns before injection when there is no carrier. Normal requests are unchanged.

Additional Notes

This PR is stacked on #12308, which is stacked on #12147.

Validation:

./gradlew :dd-java-agent:instrumentation:pekko:pekko-http-1.0:baseTestForkedTest :dd-java-agent:instrumentation:pekko:pekko-http-1.0:latestPekko10TestForkedTest :dd-java-agent:instrumentation:pekko:pekko-http-1.0:latestDepTestForkedTest --rerun-tasks
./gradlew :dd-java-agent:instrumentation:pekko:pekko-http-1.0:spotlessCheck

The forked-test matrix ran 894 cases across 18 isolated class executions: 0 failures, 0 errors, and 402 conditionally skipped cases.

muzzle could not complete locally because Maven Central range metadata resolution returned no versions for the existing pekko-http_2.12:[1.0.0,) range after retries. This PR does not change the muzzle configuration.

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]

[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.01 s	13.92 s	[-0.2%; +1.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	12.95 s	[-0.6%; +0.8%] (no difference)
startup:petclinic:appsec:Agent	17.04 s	17.35 s	[-6.1%; +2.5%] (no difference)
startup:petclinic:iast:Agent	17.34 s	17.41 s	[-1.3%; +0.4%] (no difference)
startup:petclinic:profiling:Agent	16.90 s	17.22 s	[-6.4%; +2.7%] (no difference)
startup:petclinic:sca:Agent	17.47 s	16.95 s	[-1.4%; +7.5%] (no difference)
startup:petclinic:tracing:Agent	16.46 s	16.63 s	[-2.3%; +0.1%] (no difference)

Commit: 9f6fb65b · 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]

Cool. Nice find !

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-08T14:01:35.479585Z	8adad42	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-datadog-prod-us1-2]

More details

The forked tasks use each custom Pekko test source set. The null request guard stops context injection and does not change normal requests.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[ygree]

Good catch! I wonder if there are other cases like this one where tests were mistakenly excluded from the bulk run.

[bric3]

Approving for the build.gradle changes

[AlexeyKuznetsov-DD]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-08 19:35:58 UTC ℹ️ Start processing command /merge

---

2026-09-08 19:36:04 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-08 20:31:59 UTC ℹ️ MergeQueue: This merge request was merged