Skip to content

ci: update one-pipeline to 1.5.0 - #20114

Closed
gh-worker-campaigns-3e9aa4[bot] wants to merge 2 commits into
mainfrom
engraver-auto-campaigner/update-one-pipeline-1788816083
Closed

gh-worker-campaigns-3e9aa4[bot] wants to merge 2 commits into
mainfrom
engraver-auto-campaigner/update-one-pipeline-1788816083

Conversation

@gh-worker-campaigns-3e9aa4

Copy link
Copy Markdown
Contributor

This automated pull request updates one-pipeline to 1.5.0.

📝 Full release notes

@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Sep 7, 2026 •

Copy link
Copy Markdown
Contributor

Pipelines  Tests

✨ Unblock PR with BitsAI

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 377 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-py | appsec/appsec 2/4 — ❌ 2 tests failed · 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

❌ test_user_blocking_listener_registered_without_appsec_trace_utils[py3.10] from test_appsec_trace_utils.py
STDERR: Expected [] got [b'OpenTelemetry configuration OTEL_OPERATOR_IMAGE_NAME is not supported by Datadog.\n']
❌ test_iast_source_suppression_does_not_import_iast[py3.10] from test_asm_request_context.py
STDERR: Expected [] got [b'OpenTelemetry configuration OTEL_OPERATOR_IMAGE_NAME is not supported by Datadog.\n']
DataDog/apm-reliability/dd-trace-py | appsec/appsec 3/4 — ❌ 2 tests failed · 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

❌ test_user_blocking_listener_registered_without_appsec_trace_utils[py3.11] from test_appsec_trace_utils.py
STDERR: Expected [] got [b'OpenTelemetry configuration OTEL_OPERATOR_IMAGE_NAME is not supported by Datadog.\n']
❌ test_iast_source_suppression_does_not_import_iast[py3.11] from test_asm_request_context.py
STDERR: Expected [] got [b'OpenTelemetry configuration OTEL_OPERATOR_IMAGE_NAME is not supported by Datadog.\n']
DataDog/apm-reliability/dd-trace-py | appsec/appsec 4/4 — ❌ 2 tests failed · 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

❌ test_user_blocking_listener_registered_without_appsec_trace_utils[py3.12] from test_appsec_trace_utils.py
STDERR: Expected [] got [b'OpenTelemetry configuration OTEL_OPERATOR_IMAGE_NAME is not supported by Datadog.\n']
❌ test_iast_source_suppression_does_not_import_iast[py3.12] from test_asm_request_context.py
STDERR: Expected [] got [b'OpenTelemetry configuration OTEL_OPERATOR_IMAGE_NAME is not supported by Datadog.\n']

View all 377 failed jobs.

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🔄 Datadog retried 2887 tests - 7 passed on retry View in Datadog

🚧 9 tests that failed were ignored due to quarantine View in Datadog

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: dd0a45a | Docs | View more details | Give us feedback!

@pr-commenter

pr-commenter Bot commented Sep 7, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-09-07 21:53:50

Comparing candidate commit ca07a09 in PR branch engraver-auto-campaigner/update-one-pipeline-1788816083 with baseline commit ca07a09 in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 2 performance regressions! Performance is the same for 572 metrics, 10 unstable metrics, 7 known flaky benchmarks, 17 flaky benchmarks without significant changes.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:iastaspects-join_aspect

  • 🟥 execution_time [+42.135µs; +47.055µs] or [+19.186%; +21.427%]

scenario:samplingrules-high_match

  • 🟥 execution_time [+11.483µs; +13.846µs] or [+7.291%; +8.791%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:coreapiscenario-context_with_data_listeners

  • unstable execution_time [-665.571ns; +795.836ns] or [-6.023%; +7.202%]

scenario:coreapiscenario-core_dispatch_1_listener

  • unstable execution_time [-35.003ns; +31.016ns] or [-5.716%; +5.065%]

scenario:coreapiscenario-core_dispatch_50_listeners

  • unstable execution_time [-1726.967ns; +1565.222ns] or [-10.129%; +9.181%]

scenario:coreapiscenario-core_dispatch_exception_listeners

  • unstable execution_time [-1183.108ns; +1285.320ns] or [-9.147%; +9.937%]

scenario:coreapiscenario-core_dispatch_listeners

  • unstable execution_time [-340.279ns; +308.814ns] or [-9.246%; +8.391%]

scenario:coreapiscenario-core_dispatch_no_args_listeners

  • unstable execution_time [-252.727ns; +259.517ns] or [-8.660%; +8.893%]

scenario:coreapiscenario-core_dispatch_with_results_1_listener

  • unstable execution_time [-57.708ns; +94.031ns] or [-5.023%; +8.184%]

scenario:coreapiscenario-core_dispatch_with_results_50_listeners

  • unstable execution_time [-4128.933ns; +3911.975ns] or [-10.022%; +9.495%]

scenario:coreapiscenario-core_dispatch_with_results_listeners

  • unstable execution_time [-687.846ns; +860.630ns] or [-8.496%; +10.630%]

scenario:packagesupdateimporteddependencies-import_many_stdlib_cached

  • unstable execution_time [-56485.524ns; +55300.749ns] or [-9.634%; +9.432%]

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:httppropagationinject-ids_only

  • 🟥 execution_time [+1.958µs; +2.116µs] or [+11.443%; +12.367%]

scenario:iastaspects-casefold_noaspect

  • 🟥 execution_time [+45.550µs; +51.279µs] or [+18.690%; +21.041%]

scenario:iastaspectsospath-ospathbasename_aspect

  • 🟥 execution_time [+122.913µs; +129.916µs] or [+29.916%; +31.621%]

scenario:iastaspectssplit-rsplit_aspect

  • 🟥 execution_time [+13.788µs; +19.150µs] or [+9.626%; +13.369%]

scenario:span-start

  • 🟥 execution_time [+1.544ms; +1.698ms] or [+10.657%; +11.718%]

scenario:telemetryaddmetric-1-count-metric-1-times

  • 🟥 execution_time [+501.201ns; +544.195ns] or [+18.089%; +19.641%]

scenario:tracer-small

  • 🟥 execution_time [+33.741µs; +36.594µs] or [+9.936%; +10.777%]

Known flaky benchmarks without significant changes:

  • scenario:errortrackingflasksqli-baseline
  • scenario:flasksimple-iast-get
  • scenario:iastaspects-casefold_aspect
  • scenario:iastaspects-index_aspect
  • scenario:iastaspects-ljust_noaspect
  • scenario:iastaspects-lower_aspect
  • scenario:iastaspects-replace_aspect
  • scenario:iastaspects-rstrip_aspect
  • scenario:iastaspects-swapcase_aspect
  • scenario:iastaspects-title_noaspect
  • scenario:iastaspects-translate_aspect
  • scenario:iastaspects-translate_noaspect
  • scenario:iastaspects-upper_noaspect
  • scenario:packagespackageforrootmodulemapping-cache_off
  • scenario:packagespackageforrootmodulemapping-cache_on
  • scenario:sethttpmeta-all-enabled
  • scenario:telemetryaddmetric-record-100-metrics

@emmettbutler emmettbutler added the changelog/no-changelog A changelog entry is not required for this PR. label Sep 9, 2026
@emmettbutler

Copy link
Copy Markdown
Collaborator

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 9, 2026 •

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-09 16:34:20 UTC ℹ️ Start processing command /merge


2026-09-09 16:34:27 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

  • Run /code blockers to see what is blocking it.
  • Run /remove to cancel it.

2026-09-09 21:00:11 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

@cit-pr-commenter-54b7da

Copy link
Copy Markdown

Codeowners resolved as

Resolved from the full PR diff against main using the target branch CODEOWNERS file.
CODEOWNERS team requests not listed below are not required by the current file set.

.gitlab/one-pipeline.locked.yml                                         @DataDog/python-guild @DataDog/apm-core-python

@cit-pr-commenter-54b7da

Copy link
Copy Markdown

Circular import analysis

⚠️ Existing circular imports

There are 1 circular imports that already exist on the base branch and have not been changed by this PR.

ddtrace.errortracking._handled_exceptions.bytecode_injector -> ddtrace.errortracking._handled_exceptions.callbacks -> ddtrace.errortracking._handled_exceptions.collector -> ddtrace.errortracking._handled_exceptions.bytecode_reporting -> ddtrace.errortracking._handled_exceptions.bytecode_injector

@cit-pr-commenter-54b7da

Copy link
Copy Markdown

Dependency direction analysis

⚠️ Existing dependency direction violations

There are 230 dependency direction violations that already exist on the base branch and have not been changed by this PR.

Show existing violations (showing 5 of 230 highest severity)
ddtrace.internal.tracemethods -×-> ddtrace.trace  (internal-core -> product:tracing, score=134)
ddtrace.llmobs._integrations.openai_agents -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=132)
ddtrace.llmobs._integrations.bedrock_agents -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=132)
ddtrace.debugging._exception.replay -×-> ddtrace.trace  (product:debugging -> product:tracing, score=132)
ddtrace.llmobs._telemetry -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=132)

To see all violations, download the layers-base.json and layers-pr.json artifacts from this CI job and run:

uv run --script scripts/import-analysis/layers.py compare layers-base.json layers-pr.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

campaigner-automated-change changelog/no-changelog A changelog entry is not required for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants