Enable coverage when testJvm same as Gradle Daemon JDK or with checkCoverage property

[bric3]

What Does This Do

Coverage is now enabled if the testJvm matches the daemon JDK (as before), but now also when explicitly requested via checkCoverage property which is consulted when the aggregate test task is being configured, but never was in the test jvm build extension.

Note

You can consider this as a hotfix, because checkCoverage is somewhat an unrelated property to the test jvm constraints plugin, it is a CI concern.
At some point this might be refactored to a place with the proper scoped concerns.

Motivation

Code coverage was explicitly disabled when the testJvm was run on a different JDK.

Coverage was disabled as a side effect of the old multi-JDK test optimization.

When -PtestJvm was introduced, the intent was to run the same Gradle Test tasks on another JDK instead of creating separate test tasks per JDK. For those additional JVM runs, Jacoco was explicitly disabled to avoid paying coverage instrumentation cost across the whole compatibility matrix. That made sense when coverage was expected to run only once, on the normal/base test JVM.

The problem is that CI later also passed -PtestJvm=8 to the coverage job. While that was mostly harmless, once the daemon moved to a newer JDK, Java 21, the gitlab-ci condition if [ "$testJvm" == "8" ]; then export GRADLE_PARAMS="-PskipFlakyTests -PcheckCoverage"; fi was applied, but then made the Java 8 a real test launcher. Which then deactivated jacoco.

Additional Notes

Instrumentations were deliberately not covered by jacoco, so only base_tests job is affected.

History of related changes

• Rework the way multi-jvm tests work #522
• Optimize circleci resource_class and run instrumentation tests as a separate task #2710
• Restructure MultiJDK testing to override JDK instead of creating tasks #3417
• Fix test selection logic with coverage #7467
• Introduces testJvmConstraints Gradle extension to replace extra properties #9892
• Bump spotbugs gradle plugin to 6.4.7 #10025 (Gradle daemon JDK bump to Java 21)
  • this was reverted and re-applied here Re-apply "Bump spotbugs gradle plugin to 6.4.7 (#10025)" #10074

Coverage fix PRs

• Cover continuation and listener behaviour when registering no-op manager during tests #11762
• Improve test coverage for CiVis classes #11768
• Exclude ServiceNameSources from coverage #11769
• Exclude patched OkHttp classes and trivial I/O classes from coverage #11770
• Extend OTLP HTTP coverage to GRPC #11771
• Add coverage for ForeignMemoryWriterFactory #11772
• Cover decoded trace sampling priority. #11773
• Enable and fix test coverage for SCA types in internal API #11774
• Add coverage and exclusions for dsm classes #11775
• Cover disabled ratelimited logging. #11776
• Exclude ProfilerContext from coverage #11777
• Add missing coverage tests for OptimizedTagMap and EntryReadingHelper #11778
• Add missing coverage tests for Hashtable.D2 #11779
• Add missing coverage tests for Matchers.AnyMatcher primitive overloads #11780
• Update Code Coverage for config-utils #11781
• Remove default methods from CoreSpan; implement them in test doubles #11782
• Test explicit histogram boundaries and per-thread recordings #11783
• Add FFE flag map adapter coverage #11784
• Increase SCA vulnerability test coverage #11785
• Extend WellKnownTagsTest coverage and migrate it to Java #11790
• Extend W3CTraceParentTest coverage and migrate it to Java #11791
• Add LLMObsContextTest #11792
• Add direct coverage tests for Hashtable.D2.Entry #11794
• Exclude OptimizedTagMap.EmptyHolder from coverage checks #11795
• Add TemporaryRequestContext unit tests #11798
• Add test coverage exclusion for ClientIpAddressData #11799
• Add MessageAdapter content parts serialization test coverage #11800
• Add ProtocolVersion tests and exclude specific classes from coverage #11801
• Add 128 bit TID parsing tests #11802
• Exclude OtelSpiMetricPeriodicAction from code coverage #11806

Debugger tests are not covered in ci, and live under a different aggregate task, so the next is related, but not directly handled by this PR.

• Debugger fix coverage #11807

[datadog-official]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 54.94%

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0b89105 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟡 Java Benchmark SLOs — Performance SLO warning (near threshold)

Suite	Status
Startup	🟡 warning

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.97 s	[-0.9%; +0.3%] (no difference)
startup:insecure-bank:tracing:Agent	12.86 s	13.04 s	[-2.1%; -0.6%] (maybe better)
startup:petclinic:appsec:Agent	17.49 s	16.94 s	[+2.4%; +4.1%] (significantly worse)
startup:petclinic:iast:Agent	17.46 s	17.44 s	[-0.7%; +1.0%] (no difference)
startup:petclinic:profiling:Agent	17.50 s	17.40 s	[-0.4%; +1.6%] (no difference)
startup:petclinic:sca:Agent	17.55 s	17.36 s	[+0.4%; +1.8%] (maybe worse)
startup:petclinic:tracing:Agent	16.53 s	16.17 s	[-2.1%; +6.5%] (no difference)

Commit:0b891053 · 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-06-30 15:36:04 UTC ℹ️ Start processing command /merge

---

2026-06-30 15:36:09 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-06-30 16:42:30 UTC ℹ️ MergeQueue: This merge request was merged