Clarify nested Gradle cleanup failures

[bric3]

What Does This Do

Report an existing nested Gradle user home that could not be cleaned up, with a pointer to the shutdown and cleanup warnings. Document the separate timeout budgets, the preservation policy, and the internal daemon log naming shared with the buildSrc fixture.

Motivation

Follow-up to review comment on

• Fix nested Gradle daemon cleanup races #12782

A user home preserved after uncertain daemon shutdown is currently reported as a creation failure.

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

[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-10-08T13:36:18.727130Z	480004d	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-08T13:37:03.458219Z	480004d	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.

[bric3]

@dougqh I addressed your comments here : #12782 (review)

[datadog-datadog-prod-us1-2]

More details

Retained nested Gradle user homes now produce a cleanup-specific diagnostic. The reviewed guard preserves the existing daemon shutdown, timeout, and directory-retention behavior.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 480004d · @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.96 s	13.98 s	[-1.2%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.87 s	13.03 s	[-2.0%; -0.4%] (maybe better)
startup:petclinic:appsec:Agent	16.71 s	16.82 s	[-5.0%; +3.7%] (no difference)
startup:petclinic:iast:Agent	16.80 s	16.96 s	[-1.6%; -0.2%] (maybe better)
startup:petclinic:profiling:Agent	16.62 s	16.90 s	[-2.8%; -0.5%] (maybe better)
startup:petclinic:sca:Agent	17.00 s	17.00 s	[-0.9%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.00 s	16.02 s	[-1.2%; +0.9%] (no difference)

Commit: 480004d6 · 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.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-10 15:22:59 UTC ℹ️ Start processing command /merge

---

2026-10-10 15:23:04 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-10-10 16:34:54 UTC ℹ️ MergeQueue: This merge request was merged