Fix Spring WebFlux client flaky tests

[amarziali]

What Does This Do

Consumes Spring WebFlux client response bodies before returning from test requests.

exchange().block() can return after receiving the response headers while Reactor Netty is still processing channelReadComplete. Test cleanup could consequently observe the instrumentation scope opened by fireChannelReadComplete before its exit advice closed it.

Draining the response body ensures asynchronous response processing completes before the test ends.

Motivation

Additional Notes

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]

[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-29T09:22:40.618448Z	6e65acb	PR opened
🔒 Security Review	✅ Completed 2026-09-29T09:19:33.206583Z	6e65acb	PR opened

ℹ️ 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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6e65acbcbe

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-official]

Blocking on bodyToMono(Void) does not order test cleanup after Netty’s later channelReadComplete callback, so the scope-diagnostic race this change targets can still occur.

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 6e65acb · @DataDog review to ask questions}

[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	13.99 s	14.01 s	[-0.9%; +0.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.97 s	13.07 s	[-1.6%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	17.04 s	16.95 s	[-0.4%; +1.5%] (no difference)
startup:petclinic:iast:Agent	17.04 s	17.04 s	[-0.7%; +0.7%] (no difference)
startup:petclinic:profiling:Agent	16.53 s	16.95 s	[-3.4%; -1.5%] (significantly better)
startup:petclinic:sca:Agent	16.94 s	17.00 s	[-1.2%; +0.6%] (no difference)
startup:petclinic:tracing:Agent	16.17 s	16.21 s	[-1.0%; +0.5%] (no difference)

Commit: 6720e147 · 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.

[amarziali]

@DataDog review

[datadog-official]

More details

The response helper drains each body and waits for queued Netty event-loop work before test cleanup; no concrete failure mode was identified in the changed call sites.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 6720e14 · @DataDog review to ask questions}

[amarziali]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-29 13:18:41 UTC ℹ️ Start processing command /merge

---

2026-09-29 13:18:46 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-29 13:40:04 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for cdd6b27:

• test_ssi_smoke: [25, 7/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[amarziali]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-29 14:03:38 UTC ℹ️ Start processing command /merge

---

2026-09-29 14:03:43 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-29 15:12:24 UTC ℹ️ MergeQueue: This merge request was merged