Skip to content

Bump gazelle to 0.48.0 without override - #48397

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
regis.desgroppes/bazel-gazelle-0.48.0
Mar 26, 2026
Merged

Bump gazelle to 0.48.0 without override#48397
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
regis.desgroppes/bazel-gazelle-0.48.0

Conversation

@rdesgroppes

@rdesgroppes rdesgroppes commented Mar 26, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

What does this PR do?

Bump gazelle from 0.47.0 to 0.48.0 and drop the git_override that pinned to an unreleased commit on their master.

Motivation

v0.48.0 ships both fixes the override was waiting for:

Describe how you validated your changes

bazel run //:gazelle produces no change.

@rdesgroppes rdesgroppes added changelog/no-changelog No changelog entry needed qa/no-code-change No code change in Agent code requiring validation labels Mar 26, 2026
@dd-octo-sts dd-octo-sts Bot added internal Identify a non-fork PR team/agent-build labels Mar 26, 2026
@github-actions github-actions Bot added the short review PR is simple enough to be reviewed quickly label Mar 26, 2026
@agent-platform-auto-pr

agent-platform-auto-pr Bot commented Mar 26, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Files inventory check summary

File checks results against ancestor 37509467:

Results for datadog-agent_7.79.0~devel.git.188.1778799.pipeline.104523827-1_amd64.deb:

No change detected

@agent-platform-auto-pr

agent-platform-auto-pr Bot commented Mar 26, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 3750946
📊 Static Quality Gates Dashboard
🔗 SQG Job

31 successful checks with minimal change (< 2 KiB)
Quality gate Current Size
✅ agent_deb_amd64 752.541 MiB
✅ agent_deb_amd64_fips 709.559 MiB
✅ agent_heroku_amd64 313.293 MiB
✅ agent_msi 604.784 MiB
✅ agent_rpm_amd64 752.525 MiB
✅ agent_rpm_amd64_fips 709.543 MiB
✅ agent_rpm_arm64 730.963 MiB
✅ agent_rpm_arm64_fips 690.994 MiB
✅ agent_suse_amd64 752.525 MiB
✅ agent_suse_amd64_fips 709.543 MiB
✅ agent_suse_arm64 730.963 MiB
✅ agent_suse_arm64_fips 690.994 MiB
✅ docker_agent_amd64 812.844 MiB
✅ docker_agent_arm64 816.052 MiB
✅ docker_agent_jmx_amd64 1003.759 MiB
✅ docker_agent_jmx_arm64 995.746 MiB
✅ docker_cluster_agent_amd64 203.938 MiB
✅ docker_cluster_agent_arm64 218.420 MiB
✅ docker_cws_instrumentation_amd64 7.142 MiB
✅ docker_cws_instrumentation_arm64 6.689 MiB
✅ docker_dogstatsd_amd64 39.238 MiB
✅ docker_dogstatsd_arm64 37.445 MiB
✅ dogstatsd_deb_amd64 29.881 MiB
✅ dogstatsd_deb_arm64 28.030 MiB
✅ dogstatsd_rpm_amd64 29.881 MiB
✅ dogstatsd_suse_amd64 29.881 MiB
✅ iot_agent_deb_amd64 43.270 MiB
✅ iot_agent_deb_arm64 40.320 MiB
✅ iot_agent_deb_armhf 41.068 MiB
✅ iot_agent_rpm_amd64 43.270 MiB
✅ iot_agent_suse_amd64 43.270 MiB
On-wire sizes (compressed)
Quality gate Change Size (prev → curr → max)
✅ agent_deb_amd64 +49.66 KiB (0.03% increase) 174.715 → 174.764 → 178.360
✅ agent_deb_amd64_fips -35.96 KiB (0.02% reduction) 165.345 → 165.310 → 172.790
✅ agent_heroku_amd64 -3.24 KiB (0.00% reduction) 75.001 → 74.997 → 79.970
✅ agent_msi +8.0 KiB (0.01% increase) 138.352 → 138.359 → 146.220
✅ agent_rpm_amd64 -13.34 KiB (0.01% reduction) 177.501 → 177.487 → 181.830
✅ agent_rpm_amd64_fips +20.58 KiB (0.01% increase) 167.602 → 167.622 → 173.370
✅ agent_rpm_arm64 +29.32 KiB (0.02% increase) 159.476 → 159.505 → 163.060
✅ agent_rpm_arm64_fips -21.21 KiB (0.01% reduction) 151.355 → 151.335 → 156.170
✅ agent_suse_amd64 -13.34 KiB (0.01% reduction) 177.501 → 177.487 → 181.830
✅ agent_suse_amd64_fips +20.58 KiB (0.01% increase) 167.602 → 167.622 → 173.370
✅ agent_suse_arm64 +29.32 KiB (0.02% increase) 159.476 → 159.505 → 163.060
✅ agent_suse_arm64_fips -21.21 KiB (0.01% reduction) 151.355 → 151.335 → 156.170
✅ docker_agent_amd64 neutral 268.096 MiB → 272.480
✅ docker_agent_arm64 -3.96 KiB (0.00% reduction) 255.303 → 255.299 → 261.060
✅ docker_agent_jmx_amd64 neutral 336.740 MiB → 341.100
✅ docker_agent_jmx_arm64 neutral 319.928 MiB → 325.620
✅ docker_cluster_agent_amd64 neutral 71.367 MiB → 72.920
✅ docker_cluster_agent_arm64 neutral 67.014 MiB → 68.220
✅ docker_cws_instrumentation_amd64 neutral 2.999 MiB → 3.330
✅ docker_cws_instrumentation_arm64 neutral 2.729 MiB → 3.090
✅ docker_dogstatsd_amd64 neutral 15.173 MiB → 15.820
✅ docker_dogstatsd_arm64 neutral 14.488 MiB → 14.830
✅ dogstatsd_deb_amd64 neutral 7.892 MiB → 8.790
✅ dogstatsd_deb_arm64 neutral 6.778 MiB → 7.710
✅ dogstatsd_rpm_amd64 neutral 7.903 MiB → 8.800
✅ dogstatsd_suse_amd64 neutral 7.903 MiB → 8.800
✅ iot_agent_deb_amd64 neutral 11.397 MiB → 12.040
✅ iot_agent_deb_arm64 +2.84 KiB (0.03% increase) 9.701 → 9.704 → 10.450
✅ iot_agent_deb_armhf neutral 9.940 MiB → 10.620
✅ iot_agent_rpm_amd64 -4.09 KiB (0.03% reduction) 11.421 → 11.417 → 12.060
✅ iot_agent_suse_amd64 -4.09 KiB (0.03% reduction) 11.421 → 11.417 → 12.060

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Mar 26, 2026 •
edited
Loading

Copy link
Copy Markdown

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: e6f5254a-8c2e-4f2e-9121-7e06620d10ea

Baseline: f7e8aee
Comparison: 1a4e7f5
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI trials links
➖ docker_containers_cpu % cpu utilization +0.83 [-2.19, +3.84] 1 Logs

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
➖ quality_gate_logs % cpu utilization +1.68 [+0.07, +3.29] 1 Logs bounds checks dashboard
➖ tcp_syslog_to_blackhole ingress throughput +1.22 [+1.09, +1.35] 1 Logs
➖ docker_containers_cpu % cpu utilization +0.83 [-2.19, +3.84] 1 Logs
➖ quality_gate_metrics_logs memory utilization +0.55 [+0.32, +0.78] 1 Logs bounds checks dashboard
➖ docker_containers_memory memory utilization +0.45 [+0.38, +0.52] 1 Logs
➖ ddot_metrics memory utilization +0.14 [-0.04, +0.32] 1 Logs
➖ file_to_blackhole_100ms_latency egress throughput +0.04 [-0.02, +0.10] 1 Logs
➖ ddot_metrics_sum_delta memory utilization +0.04 [-0.14, +0.21] 1 Logs
➖ file_to_blackhole_500ms_latency egress throughput +0.04 [-0.36, +0.43] 1 Logs
➖ file_to_blackhole_1000ms_latency egress throughput +0.02 [-0.43, +0.46] 1 Logs
➖ tcp_dd_logs_filter_exclude ingress throughput +0.01 [-0.10, +0.12] 1 Logs
➖ uds_dogstatsd_to_api ingress throughput +0.01 [-0.20, +0.21] 1 Logs
➖ file_to_blackhole_0ms_latency egress throughput +0.00 [-0.48, +0.48] 1 Logs
➖ otlp_ingest_logs memory utilization -0.00 [-0.10, +0.09] 1 Logs
➖ ddot_metrics_sum_cumulativetodelta_exporter memory utilization -0.00 [-0.23, +0.22] 1 Logs
➖ uds_dogstatsd_to_api_v3 ingress throughput -0.01 [-0.21, +0.20] 1 Logs
➖ file_tree memory utilization -0.01 [-0.07, +0.05] 1 Logs
➖ ddot_metrics_sum_cumulative memory utilization -0.10 [-0.24, +0.04] 1 Logs
➖ otlp_ingest_metrics memory utilization -0.20 [-0.36, -0.04] 1 Logs
➖ ddot_logs memory utilization -0.22 [-0.29, -0.16] 1 Logs
➖ uds_dogstatsd_20mb_12k_contexts_20_senders memory utilization -0.28 [-0.33, -0.22] 1 Logs
➖ quality_gate_idle_all_features memory utilization -0.28 [-0.32, -0.24] 1 Logs bounds checks dashboard
➖ quality_gate_idle memory utilization -0.59 [-0.63, -0.54] 1 Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed observed_value links
✅ docker_containers_cpu simple_check_run 10/10 743 ≥ 26
✅ docker_containers_memory memory_usage 10/10 271.99MiB ≤ 370MiB
✅ docker_containers_memory simple_check_run 10/10 724 ≥ 26
✅ file_to_blackhole_0ms_latency memory_usage 10/10 0.19GiB ≤ 1.20GiB
✅ file_to_blackhole_0ms_latency missed_bytes 10/10 0B = 0B
✅ file_to_blackhole_1000ms_latency memory_usage 10/10 0.23GiB ≤ 1.20GiB
✅ file_to_blackhole_1000ms_latency missed_bytes 10/10 0B = 0B
✅ file_to_blackhole_100ms_latency memory_usage 10/10 0.20GiB ≤ 1.20GiB
✅ file_to_blackhole_100ms_latency missed_bytes 10/10 0B = 0B
✅ file_to_blackhole_500ms_latency memory_usage 10/10 0.21GiB ≤ 1.20GiB
✅ file_to_blackhole_500ms_latency missed_bytes 10/10 0B = 0B
✅ quality_gate_idle intake_connections 10/10 3 = 3 bounds checks dashboard
✅ quality_gate_idle memory_usage 10/10 174.10MiB ≤ 175MiB bounds checks dashboard
✅ quality_gate_idle_all_features intake_connections 10/10 3 = 3 bounds checks dashboard
✅ quality_gate_idle_all_features memory_usage 10/10 494.69MiB ≤ 550MiB bounds checks dashboard
✅ quality_gate_logs intake_connections 10/10 4 ≤ 6 bounds checks dashboard
✅ quality_gate_logs memory_usage 10/10 204.88MiB ≤ 220MiB bounds checks dashboard
✅ quality_gate_logs missed_bytes 10/10 0B = 0B bounds checks dashboard
✅ quality_gate_metrics_logs cpu_usage 10/10 348.34 ≤ 2000 bounds checks dashboard
✅ quality_gate_metrics_logs intake_connections 10/10 4 ≤ 6 bounds checks dashboard
✅ quality_gate_metrics_logs memory_usage 10/10 413.54MiB ≤ 475MiB bounds checks dashboard
✅ quality_gate_metrics_logs missed_bytes 10/10 0B = 0B bounds checks dashboard

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

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.

@rdesgroppes
rdesgroppes force-pushed the regis.desgroppes/bazel-gazelle-0.48.0 branch from d79bc86 to b414899 Compare March 26, 2026 13:02
@rdesgroppes rdesgroppes changed the title Regis.desgroppes/bazel gazelle 0.48.0 Bump gazelle to 0.48.0 (no longer overridden) Mar 26, 2026
@rdesgroppes rdesgroppes changed the title Bump gazelle to 0.48.0 (no longer overridden) Bump gazelle to 0.48.0 without override Mar 26, 2026
@rdesgroppes
rdesgroppes marked this pull request as ready for review March 26, 2026 13:04
@rdesgroppes
rdesgroppes requested a review from a team as a code owner March 26, 2026 13:04
@rdesgroppes
Bump gazelle to 0.48.0 (no longer overriden)
1778799 
### What does this PR do?
Bump `gazelle` from 0.47.0 to 0.48.0 and drop the `git_override` that
pinned to an unreleased commit on their `master`.

### Motivation
v0.48.0 ships both fixes the override was waiting for:
- bazel-contrib/bazel-gazelle#2274
- bazel-contrib/bazel-gazelle#2284

### Describe how you validated your changes
`bazel run //:gazelle` produces no change.
@rdesgroppes
rdesgroppes force-pushed the regis.desgroppes/bazel-gazelle-0.48.0 branch from b414899 to 1778799 Compare March 26, 2026 13:05
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 1a4e7f5 into main Mar 26, 2026
255 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the regis.desgroppes/bazel-gazelle-0.48.0 branch March 26, 2026 14:22
@github-actions github-actions Bot added this to the 7.79.0 milestone Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JSGette JSGette JSGette approved these changes

Assignees

No one assigned

Labels

changelog/no-changelog No changelog entry needed internal Identify a non-fork PR qa/no-code-change No code change in Agent code requiring validation short review PR is simple enough to be reviewed quickly team/agent-build

Projects

None yet

Milestone

7.79.0

Development

Successfully merging this pull request may close these issues.

2 participants

@rdesgroppes @JSGette