Make dd-trace-java.test-jvm-constraints report architecture in test task inputs

[bric3]

What Does This Do

Track the JVM operating system and architecture as inputs of each Test task configured by dd-trace-java.test-jvm-constraints.

Motivation

Changing operating systems or architectures could currently reuse test results from the same Java version and vendor. This makes platform changes invalidate both up-to-date checks and build-cache entries.

Follow-up to #12630 and aligned with #12631. Context #12604

Additional Notes

The platform uses the JVM-reported os.name and os.arch values.

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-09-24T20:13:31.003485Z	ecfbe90	Draft marked ready
🔒 Security Review	✅ Completed 2026-09-24T20:13:32.903006Z	ecfbe90	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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ecfbe904b8

ℹ️ 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-prod-us1-5]

The new input records the Gradle daemon architecture. A test launcher with another architecture can still reuse stale cached results.

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit ecfbe90 · @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.93 s	13.93 s	[-1.0%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	13.01 s	[-1.1%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	17.07 s	16.92 s	[+0.1%; +1.7%] (maybe worse)
startup:petclinic:iast:Agent	17.00 s	17.00 s	[-0.8%; +0.8%] (no difference)
startup:petclinic:profiling:Agent	16.66 s	16.87 s	[-2.3%; -0.1%] (maybe better)
startup:petclinic:sca:Agent	16.87 s	16.68 s	[+0.2%; +2.1%] (maybe worse)
startup:petclinic:tracing:Agent	16.09 s	16.07 s	[-0.8%; +1.1%] (no difference)

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

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-24 21:43:01 UTC ℹ️ Start processing command /merge

---

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

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

---

2026-09-24 22:47:57 UTC ℹ️ MergeQueue: This merge request was merged