Skip to content

Conversation

@campaigner-prod
Copy link
Contributor

Do not merge this PR. This is just for testing the next docker in
docker arm64 execution env with a real use case.
Campaign ran by @jorgetomtz

@github-actions github-actions bot added the area/ci CI/CD, automated testing, etc. label Dec 19, 2025
@pr-commenter
Copy link

pr-commenter bot commented Dec 19, 2025

Binary Size Analysis (Agent Data Plane)

Target: 40e71d4 (baseline) vs 59d7506 (comparison) diff
Baseline Size: 335.89 MiB
Comparison Size: 335.89 MiB
Size Change: +0 B (+0.00%)
Pass/Fail Threshold: +5%
Result: PASSED ✅

Changes by Module

Module File Size Symbols
anon.6963da505859e1c5d18d13cd64b99327.1.llvm.10922851595922426980 +130 B 1
anon.6963da505859e1c5d18d13cd64b99327.1.llvm.15439033637761327086 -130 B 1
anon.6963da505859e1c5d18d13cd64b99327.4.llvm.10922851595922426980 +115 B 1
anon.6963da505859e1c5d18d13cd64b99327.4.llvm.15439033637761327086 -115 B 1
anon.6963da505859e1c5d18d13cd64b99327.3.llvm.10922851595922426980 +109 B 1
anon.6963da505859e1c5d18d13cd64b99327.3.llvm.15439033637761327086 -109 B 1
anon.6963da505859e1c5d18d13cd64b99327.0.llvm.10922851595922426980 +97 B 1
anon.6963da505859e1c5d18d13cd64b99327.0.llvm.15439033637761327086 -97 B 1
anon.6963da505859e1c5d18d13cd64b99327.2.llvm.10922851595922426980 +95 B 1
anon.6963da505859e1c5d18d13cd64b99327.2.llvm.15439033637761327086 -95 B 1

Detailed Symbol Changes

    FILE SIZE        VM SIZE    
 --------------  -------------- 
  [NEW]    +130  [NEW]     +40    anon.6963da505859e1c5d18d13cd64b99327.1.llvm.10922851595922426980
  [NEW]    +115  [NEW]     +25    anon.6963da505859e1c5d18d13cd64b99327.4.llvm.10922851595922426980
  [NEW]    +109  [NEW]     +19    anon.6963da505859e1c5d18d13cd64b99327.3.llvm.10922851595922426980
  [NEW]     +97  [NEW]      +7    anon.6963da505859e1c5d18d13cd64b99327.0.llvm.10922851595922426980
  [NEW]     +95  [NEW]      +5    anon.6963da505859e1c5d18d13cd64b99327.2.llvm.10922851595922426980
  [DEL]     -95  [DEL]      -5    anon.6963da505859e1c5d18d13cd64b99327.2.llvm.15439033637761327086
  [DEL]     -97  [DEL]      -7    anon.6963da505859e1c5d18d13cd64b99327.0.llvm.15439033637761327086
  [DEL]    -109  [DEL]     -19    anon.6963da505859e1c5d18d13cd64b99327.3.llvm.15439033637761327086
  [DEL]    -115  [DEL]     -25    anon.6963da505859e1c5d18d13cd64b99327.4.llvm.15439033637761327086
  [DEL]    -130  [DEL]     -40    anon.6963da505859e1c5d18d13cd64b99327.1.llvm.15439033637761327086
  [ = ]       0  [ = ]       0    TOTAL

@pr-commenter
Copy link

pr-commenter bot commented Dec 19, 2025

Regression Detector (Agent Data Plane)

Regression Detector Results

Run ID: 77a9e97d-53f3-4a5c-afa4-c9bb341d427d

Baseline: 40e71d4
Comparison: 59d7506
Diff

❌ Experiments with retried target crashes

This is a critical error. One or more replicates failed with a non-zero exit code. These replicates may have been retried. See Replicate Execution Details for more information.

  • otlp_ingest_metrics_adp
  • quality_gates_rss_dsd_heavy
  • quality_gates_rss_dsd_ultraheavy

Optimization Goals: ✅ Improvement(s) detected

perf experiment goal Δ mean % Δ mean % CI trials links
otlp_ingest_logs_adp memory utilization -5.65 [-6.01, -5.29] 1 (metrics) (profiles) (logs)

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
otlp_ingest_metrics_adp memory utilization +1.17 [+0.97, +1.37] 1
quality_gates_rss_dsd_heavy memory utilization +0.14 [+0.01, +0.28] 1 (metrics) (profiles) (logs)
dsd_uds_100mb_3k_contexts_throughput ingress throughput +0.02 [-0.03, +0.07] 1 (metrics) (profiles) (logs)
quality_gates_rss_dsd_ultraheavy ingress throughput +0.00 [-0.06, +0.06] 1 (metrics) (profiles) (logs)
dsd_uds_512kb_3k_contexts_throughput ingress throughput -0.00 [-0.05, +0.05] 1 (metrics) (profiles) (logs)
dsd_uds_1mb_3k_contexts_throughput ingress throughput -0.00 [-0.06, +0.06] 1 (metrics) (profiles) (logs)
dsd_uds_10mb_3k_contexts_throughput ingress throughput -0.01 [-0.18, +0.16] 1 (metrics) (profiles) (logs)
quality_gates_rss_dsd_medium memory utilization -0.04 [-0.22, +0.14] 1 (metrics) (profiles) (logs)
quality_gates_rss_idle memory utilization -0.19 [-0.22, -0.15] 1 (metrics) (profiles) (logs)
quality_gates_rss_dsd_low memory utilization -0.32 [-0.47, -0.17] 1 (metrics) (profiles) (logs)
dsd_uds_500mb_3k_contexts_throughput ingress throughput -0.77 [-0.91, -0.64] 1 (metrics) (profiles) (logs)
otlp_ingest_logs_adp memory utilization -5.65 [-6.01, -5.29] 1 (metrics) (profiles) (logs)

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed links
quality_gates_rss_dsd_heavy memory_usage 10/10 (metrics) (profiles) (logs)
quality_gates_rss_dsd_low memory_usage 10/10 (metrics) (profiles) (logs)
quality_gates_rss_dsd_medium memory_usage 10/10 (metrics) (profiles) (logs)
quality_gates_rss_dsd_ultraheavy memory_usage 10/10 (metrics) (profiles) (logs)
quality_gates_rss_idle memory_usage 10/10 (metrics) (profiles) (logs)

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment Variant Replicates Failure Logs Debug Dashboard
experiment_with_failures baseline 0 (x8) 1 (x6) Oom killed Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Normal Replicate Execution Failures (non-profiling)

Experiment Variant Replicates Failure Debug Dashboard
otlp_ingest_metrics_adp comparison 8 Failed to shutdown when requested Debug Dashboard
quality_gates_rss_dsd_heavy comparison 8 Failed to shutdown when requested Debug Dashboard
quality_gates_rss_dsd_ultraheavy baseline 6, 0 Failed to shutdown when requested Debug Dashboard
quality_gates_rss_dsd_ultraheavy comparison 4 Failed to shutdown when requested Debug Dashboard

@jorgetomtz
Copy link

/ddci trigger

@gh-worker-devflow-routing-ef8351
Copy link

gh-worker-devflow-routing-ef8351 bot commented Jan 16, 2026

View all feedbacks in Devflow UI.

2026-01-16 16:30:51 UTC ℹ️ Start processing command /ddci trigger


2026-01-16 16:31:11 UTC ℹ️ Devflow: /ddci trigger

✅ Tasks request sent successfully.
🔑 DDCI Request ID: 6174490983994190304
🔍 Debug this request with Datadog Traces

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

Labels

area/ci CI/CD, automated testing, etc. campaigner-automated-change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants