Update Code Coverage for config-utils

[mhlidd]

What Does This Do

Update Code Coverage for config-utils

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
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[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	14.06 s	14.00 s	[-0.3%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent	13.03 s	12.97 s	[-0.6%; +1.5%] (no difference)
startup:petclinic:appsec:Agent	16.84 s	16.65 s	[+0.0%; +2.2%] (maybe worse)
startup:petclinic:iast:Agent	16.73 s	16.98 s	[-2.4%; -0.6%] (maybe better)
startup:petclinic:profiling:Agent	16.87 s	16.93 s	[-1.3%; +0.7%] (no difference)
startup:petclinic:sca:Agent	16.99 s	16.67 s	[+1.1%; +2.7%] (significantly worse)
startup:petclinic:tracing:Agent	16.01 s	16.18 s	[-1.8%; -0.2%] (maybe better)

Commit:4f7fe135 · 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-06-29 15:40:12 UTC ℹ️ Start processing command /merge

---

2026-06-29 15:40:18 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

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