Skip to content

Improving smoke test capabilities - #12051

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 8 commits into
masterfrom
bbujon/smoke-tests-tooling
Sep 5, 2026
Merged

Improving smoke test capabilities#12051
gh-worker-dd-mergequeue-cf854d[bot] merged 8 commits into
masterfrom
bbujon/smoke-tests-tooling

Conversation

@PerfectSlayer

@PerfectSlayer PerfectSlayer commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

What Does This Do

This PR contains the follow up changes from all the other PRs of the stack.
In particular:

  • Add span link support to decoded spans and their assert rules
  • Remove test agent check customization (scope creep, not actionable in CI).

Motivation

Follow up changes from PR reviews listed in the additional notes.

Additional Notes

Related pull-requests:

Contributor Checklist

Jira ticket: APMLP-1247

@PerfectSlayer PerfectSlayer added type: feature Enhancements and improvements comp: testing Testing tag: do not merge Do not merge changes labels Jul 23, 2026
@PerfectSlayer
PerfectSlayer force-pushed the bbujon/smoke-tests-tooling branch from 29804b8 to 817d668 Compare July 28, 2026 08:49
@datadog-prod-us1-5

This comment has been minimized.

@PerfectSlayer
PerfectSlayer force-pushed the bbujon/smoke-tests-tooling branch from 817d668 to c659547 Compare July 28, 2026 09:11
@dd-octo-sts

dd-octo-sts Bot commented Jul 28, 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 14.74 s 14.67 s [-0.5%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent 13.64 s 13.72 s [-1.2%; +0.1%] (no difference)
startup:petclinic:appsec:Agent 17.09 s 16.95 s [-0.0%; +1.7%] (no difference)
startup:petclinic:iast:Agent 16.93 s 17.03 s [-1.4%; +0.2%] (no difference)
startup:petclinic:profiling:Agent 16.75 s 16.88 s [-1.8%; +0.3%] (no difference)
startup:petclinic:sca:Agent 16.33 s 16.91 s [-8.8%; +1.9%] (unstable)
startup:petclinic:tracing:Agent 16.18 s 16.02 s [+0.1%; +1.9%] (maybe worse)

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

@datadog-prod-us1-5

datadog-prod-us1-5 Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

View session in Datadog

Bits Code status: ✅ Done

Comment @DataDog to request changes

@PerfectSlayer
PerfectSlayer force-pushed the bbujon/smoke-tests-tooling branch from c659547 to 089af14 Compare July 29, 2026 06:09
@PerfectSlayer
PerfectSlayer force-pushed the bbujon/smoke-tests-tooling branch 6 times, most recently from f45d96b to 89f412f Compare August 7, 2026 08:13
@PerfectSlayer
PerfectSlayer force-pushed the bbujon/smoke-tests-tooling branch 2 times, most recently from e39c84d to adca11c Compare August 13, 2026 12:33
@PerfectSlayer
PerfectSlayer force-pushed the bbujon/smoke-tests-tooling branch 9 times, most recently from d28d501 to 18ce2e4 Compare August 27, 2026 09:13
@PerfectSlayer
PerfectSlayer changed the base branch from master to bbujon/smoke-tests-documentation August 27, 2026 09:14
@PerfectSlayer PerfectSlayer removed the tag: do not merge Do not merge changes label Aug 27, 2026
@PerfectSlayer
PerfectSlayer marked this pull request as ready for review August 27, 2026 09:32
@bric3

bric3 commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Don't you think the final PR of the stack could sum up the whole work?
Would you rather have it limited to the last change only?

Having a summary of earlier work is OK, but the PR itself should precisely describe its change it tries to get in the repo not the previous ones. If the commit landing in git is too broad then it misleads. Gicen the title is used in git it should be tailored to the PR's changes.

In this case the commit will be "Improving smoke test capabilities" but it really is about span links harness tooling.

So yes I think the description should be focused on the changes. And possibly have a specific section that explain the complete set of work required to get there. Alternatively, I think it might be better to use an issue to track work.

@PerfectSlayer

PerfectSlayer commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator Author

So yes I think the description should be focused on the changes.

At first, I thought about having another PR to stack for those changes, and keep this PR as the "preview full stack PR", still in draft. But as PR management / reviews become too painful, I did not want to go the clean way. I already baby sit PRs from 8am to 9pm so until we fix it, I'm not sure I will keep doing the "clean way". PRs are already way worst in the repo 😢

If the commit landing in git is too broad then it misleads

Commit log became significantly worse since merge queues… I don't use it anymore and not sure people still care about what is going in 😞 Anyway, I moved all the text behind HTLM comments so I can still read it but it won't be displayed.

@bric3

bric3 commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

@PerfectSlayer Don't worry I get you 😢

@ygree

ygree commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 1, 2026

Copy link
Copy Markdown

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-01T18:29:54.123005Z 3b675f0 Manual request
ℹ️ 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 chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3b675f00e7

ℹ️ 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".

Comment thread dd-smoke-tests/src/main/java/datadog/smoketest/trace/SpanLinkMatcher.java Outdated
@PerfectSlayer
PerfectSlayer force-pushed the bbujon/smoke-tests-tooling branch from acfa565 to 8559be0 Compare September 3, 2026 07:15

@ygree ygree 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.

IDM mostly approves, except for a couple of places where I left notes

@PerfectSlayer

Copy link
Copy Markdown
Collaborator Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 5, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-05 12:17:25 UTC ℹ️ Start processing command /merge


2026-09-05 12:17:30 UTC ℹ️ MergeQueue: pull request added to the queue

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


2026-09-05 12:38:26 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 9b62f99:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@PerfectSlayer

Copy link
Copy Markdown
Collaborator Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 5, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-05 12:39:45 UTC ℹ️ Start processing command /merge


2026-09-05 12:39:50 UTC ℹ️ MergeQueue: pull request added to the queue

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


2026-09-05 12:56:45 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for b144ae4:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@PerfectSlayer

Copy link
Copy Markdown
Collaborator Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 5, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-05 13:01:17 UTC ℹ️ Start processing command /merge


2026-09-05 13:01:22 UTC ℹ️ MergeQueue: pull request added to the queue

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


2026-09-05 13:49:49 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 62eea7f:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@PerfectSlayer

Copy link
Copy Markdown
Collaborator Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 5, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-05 18:02:07 UTC ℹ️ Start processing command /merge


2026-09-05 18:02:13 UTC ℹ️ MergeQueue: pull request added to the queue

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


2026-09-05 18:50:11 UTC ℹ️ MergeQueue: This merge request was merged

@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 8ff7f46 into master Sep 5, 2026
600 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the bbujon/smoke-tests-tooling branch September 5, 2026 18:50
@github-actions github-actions Bot added this to the 1.66.0 milestone Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: testing Testing type: feature Enhancements and improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants