Mark testDynamicInstrumentationEnablementWithLineProbe as Flaky

[sarahchen6]

What Does This Do

Mark testDynamicInstrumentationEnablementWithLineProbe() as Flaky

Motivation

Green CI

Additional Notes

For failure examples, see:

• GitLab job: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-java/-/jobs/1857686266
• CI/CD Optimization list

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-5]

More details

The @Flaky annotation is correctly applied — it uses the already-imported datadog.trace.test.util.Flaky, follows the identical pattern used by testExceptionReplayEnablementFailure in the same class, emits the JUnit5 "flaky" tag consumed by Gradle's skip/run flaky-test properties, and the test_flaky CI job explicitly targets :debuggerTest with CONTINUE_ON_FAILURE: true. The class-level @NonRetryable does not interfere (it controls the test-retry plugin, not JUnit5 tag-based test selection).

Was this helpful? React 👍 or 👎

_{📊 Validated against 4 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit d21c429 · What is Autotest? · 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	13.98 s	13.93 s	[-0.4%; +1.1%] (no difference)
startup:insecure-bank:tracing:Agent	12.98 s	13.03 s	[-1.1%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	16.98 s	16.87 s	[-0.4%; +1.7%] (no difference)
startup:petclinic:iast:Agent	16.96 s	16.43 s	[-1.2%; +7.6%] (no difference)
startup:petclinic:profiling:Agent	16.81 s	16.93 s	[-1.8%; +0.5%] (no difference)
startup:petclinic:sca:Agent	16.86 s	16.87 s	[-1.0%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.19 s	16.11 s	[-0.8%; +1.8%] (no difference)

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

[sarahchen6]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-14 17:27:27 UTC ℹ️ Start processing command /merge

---

2026-07-14 17:27:31 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-07-14 19:01:59 UTC ℹ️ MergeQueue: This merge request was merged