Skip to content

Cover continuation and listener behaviour when registering no-op manager during tests#11762

Open
mcculls wants to merge 2 commits into
masterfrom
mcculls/context-coverage
Open

Cover continuation and listener behaviour when registering no-op manager during tests#11762
mcculls wants to merge 2 commits into
masterfrom
mcculls/context-coverage

Conversation

@mcculls

@mcculls mcculls commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Motivation

Get ./gradlew :components:context:check to pass locally

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]

mcculls added 2 commits June 29, 2026 11:00
…Impl

(couple of branches involve a nanosecond CAS race that can't be reliably reproduced)
@mcculls mcculls requested a review from a team as a code owner June 29, 2026 10:01
@mcculls mcculls added the comp: testing Testing label Jun 29, 2026
@mcculls mcculls requested review from sarahchen6 and removed request for a team June 29, 2026 10:01
@mcculls mcculls added tag: no release notes Changes to exclude from release notes type: refactoring labels Jun 29, 2026
@mcculls mcculls requested a review from PerfectSlayer June 29, 2026 10:02
@dd-octo-sts

dd-octo-sts Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

🟢 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.99 s 13.95 s [-0.5%; +1.1%] (no difference)
startup:insecure-bank:tracing:Agent 12.92 s 13.04 s [-1.5%; -0.2%] (maybe better)
startup:petclinic:appsec:Agent 16.88 s 16.61 s [+0.6%; +2.6%] (maybe worse)
startup:petclinic:iast:Agent 16.95 s 17.01 s [-1.2%; +0.4%] (no difference)
startup:petclinic:profiling:Agent 16.87 s 16.91 s [-1.0%; +0.6%] (no difference)
startup:petclinic:sca:Agent 16.90 s 16.32 s [-1.1%; +8.2%] (no difference)
startup:petclinic:tracing:Agent 16.18 s 15.59 s [-0.4%; +8.0%] (no difference)

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

@PerfectSlayer PerfectSlayer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good for the test changes but I would rather have @bric3 to review impact of afterEvaluate use 🙏

extra["excludedClassesBranchCoverage"] =
listOf("datadog.context.ThreadLocalContextManager.ContextContinuationImpl")

afterEvaluate {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting review from @bric3 about afterEvaluate usage

@mcculls mcculls requested a review from bric3 June 29, 2026 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: testing Testing tag: no release notes Changes to exclude from release notes type: refactoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants