Bump `rules_cc` with explicit loads for Bazel 9 by rdesgroppes · Pull Request #47716 · DataDog/datadog-agent

rdesgroppes · 2026-03-11T12:36:04Z

What does this PR do?

Bump rules_cc from 0.2.8 to 0.2.17 (latest BCR release) and replace implicit global cc_* rule usage in our BUILD.bazel files with explicit loads from @rules_cc//cc:defs.bzl.

Motivation

Bazel has long deprecated injecting cc_library, cc_shared_library, cc_binary, cc_import and cc_test as built-in globals.

Making the loads explicit is the correct practice regardless of Bazel version, and is a prerequisite for the upcoming Bazel 9 bump where those globals are removed entirely.

Bump `rules_cc` from 0.2.8 to 0.2.17 (latest BCR release) and replace implicit global `cc_*` rule usage in our `BUILD.bazel` files with explicit loads from `@rules_cc//cc:defs.bzl`. Bazel has long deprecated injecting `cc_library`, `cc_shared_library`, `cc_binary`, `cc_import` and `cc_test` as built-in globals. Making the `load`s explicit is the correct practice regardless of Bazel version, and is a prerequisite for the upcoming Bazel 9 bump where those globals are removed entirely.

agent-platform-auto-pr · 2026-03-11T13:24:41Z

Files inventory check summary

File checks results against ancestor bf47cd83:

Results for datadog-agent_7.78.0~devel.git.505.8d4f57c.pipeline.101848040-1_amd64.deb:

No change detected

agent-platform-auto-pr · 2026-03-11T13:32:29Z

Static quality checks

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

31 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	746.900 MiB
✅	agent_deb_amd64_fips	705.232 MiB
✅	agent_heroku_amd64	311.738 MiB
✅	agent_msi	609.806 MiB
✅	agent_rpm_amd64	746.884 MiB
✅	agent_rpm_amd64_fips	705.216 MiB
✅	agent_rpm_arm64	724.770 MiB
✅	agent_rpm_arm64_fips	686.112 MiB
✅	agent_suse_amd64	746.884 MiB
✅	agent_suse_amd64_fips	705.216 MiB
✅	agent_suse_arm64	724.770 MiB
✅	agent_suse_arm64_fips	686.112 MiB
✅	docker_agent_amd64	807.222 MiB
✅	docker_agent_arm64	809.913 MiB
✅	docker_agent_jmx_amd64	998.137 MiB
✅	docker_agent_jmx_arm64	989.608 MiB
✅	docker_cluster_agent_amd64	203.665 MiB
✅	docker_cluster_agent_arm64	218.100 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.631 MiB
✅	docker_dogstatsd_arm64	36.939 MiB
✅	dogstatsd_deb_amd64	29.855 MiB
✅	dogstatsd_deb_arm64	28.008 MiB
✅	dogstatsd_rpm_amd64	29.855 MiB
✅	dogstatsd_suse_amd64	29.855 MiB
✅	iot_agent_deb_amd64	43.068 MiB
✅	iot_agent_deb_arm64	40.126 MiB
✅	iot_agent_deb_armhf	40.870 MiB
✅	iot_agent_rpm_amd64	43.068 MiB
✅	iot_agent_suse_amd64	43.068 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+2.46 KiB (0.00% increase)	174.431 → 174.434 → 177.700
✅	agent_deb_amd64_fips	-16.89 KiB (0.01% reduction)	165.370 → 165.354 → 172.230
✅	agent_heroku_amd64	+3.19 KiB (0.00% increase)	75.165 → 75.168 → 79.970
✅	agent_msi	neutral	138.047 MiB → 146.220
✅	agent_rpm_amd64	-11.27 KiB (0.01% reduction)	176.409 → 176.398 → 180.780
✅	agent_rpm_amd64_fips	+9.45 KiB (0.01% increase)	168.126 → 168.135 → 173.370
✅	agent_rpm_arm64	+48.76 KiB (0.03% increase)	159.273 → 159.320 → 161.610
✅	agent_rpm_arm64_fips	-16.8 KiB (0.01% reduction)	151.427 → 151.411 → 155.910
✅	agent_suse_amd64	-11.27 KiB (0.01% reduction)	176.409 → 176.398 → 180.780
✅	agent_suse_amd64_fips	+9.45 KiB (0.01% increase)	168.126 → 168.135 → 173.370
✅	agent_suse_arm64	+48.76 KiB (0.03% increase)	159.273 → 159.320 → 161.610
✅	agent_suse_arm64_fips	-16.8 KiB (0.01% reduction)	151.427 → 151.411 → 155.910
✅	docker_agent_amd64	-5.19 KiB (0.00% reduction)	267.118 → 267.113 → 271.240
✅	docker_agent_arm64	+2.68 KiB (0.00% increase)	254.427 → 254.430 → 259.800
✅	docker_agent_jmx_amd64	-6.85 KiB (0.00% reduction)	335.776 → 335.769 → 339.870
✅	docker_agent_jmx_arm64	+14.6 KiB (0.00% increase)	319.066 → 319.080 → 324.390
✅	docker_cluster_agent_amd64	neutral	71.287 MiB → 72.920
✅	docker_cluster_agent_arm64	neutral	66.913 MiB → 68.220
✅	docker_cws_instrumentation_amd64	neutral	2.995 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.727 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	14.947 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.284 MiB → 14.830
✅	dogstatsd_deb_amd64	-2.07 KiB (0.03% reduction)	7.889 → 7.887 → 8.790
✅	dogstatsd_deb_arm64	neutral	6.773 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.898 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.898 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.356 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.666 MiB → 10.450
✅	iot_agent_deb_armhf	neutral	9.896 MiB → 10.620
✅	iot_agent_rpm_amd64	neutral	11.375 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.375 MiB → 12.060

rdesgroppes · 2026-03-11T13:44:43Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-03-11T13:44:47Z

View all feedbacks in Devflow UI.

2026-03-11 13:44:46 UTC ℹ️ Start processing command /merge

2026-03-11 13:44:51 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 51m (p90).

2026-03-11 14:16:32 UTC ℹ️ MergeQueue: This merge request was merged

cit-pr-commenter-54b7da · 2026-03-11T13:56:21Z

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: d626f03b-c3b8-41b1-bb9a-aa169c3f776f

Baseline: 9323ce8
Comparison: dbf2b24
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	-2.24	[-5.19, +0.71]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	ddot_metrics	memory utilization	+0.50	[+0.31, +0.68]	1	Logs
➖	quality_gate_idle	memory utilization	+0.17	[+0.12, +0.22]	1	Logs bounds checks dashboard
➖	file_tree	memory utilization	+0.16	[+0.10, +0.21]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+0.14	[+0.02, +0.27]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.05	[-0.38, +0.48]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.05	[-0.33, +0.43]	1	Logs
➖	otlp_ingest_logs	memory utilization	+0.03	[-0.06, +0.12]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.17, +0.18]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.00	[-0.47, +0.48]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.10, +0.10]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.01	[-0.18, +0.16]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.04	[-0.18, +0.11]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.05	[-0.10, +0.00]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.05	[-0.28, +0.17]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.06	[-0.13, -0.00]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.18	[-0.22, -0.14]	1	Logs bounds checks dashboard
➖	otlp_ingest_metrics	memory utilization	-0.27	[-0.42, -0.12]	1	Logs
➖	ddot_logs	memory utilization	-0.33	[-0.39, -0.26]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.34	[-1.92, +1.23]	1	Logs bounds checks dashboard
➖	docker_containers_memory	memory utilization	-0.36	[-0.44, -0.28]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	-0.39	[-0.56, -0.23]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-0.49	[-0.73, -0.24]	1	Logs bounds checks dashboard
➖	docker_containers_cpu	% cpu utilization	-2.24	[-5.19, +0.71]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	docker_containers_cpu	simple_check_run	10/10	740 ≥ 26
✅	docker_containers_memory	memory_usage	10/10	271.52MiB ≤ 370MiB
✅	docker_containers_memory	simple_check_run	10/10	699 ≥ 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.22GiB ≤ 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	172.15MiB ≤ 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	491.44MiB ≤ 550MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	208.18MiB ≤ 220MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	354.84 ≤ 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	402.23MiB ≤ 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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
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_metrics_logs, bounds check cpu_usage: 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.
quality_gate_metrics_logs, bounds check missed_bytes: 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 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.

### What does this PR do? Bump `rules_cc` from 0.2.8 to 0.2.17 (latest BCR release) and replace implicit global `cc_*` rule usage in our `BUILD.bazel` files with explicit loads from `@rules_cc//cc:defs.bzl`. ### Motivation Bazel has long deprecated injecting `cc_library`, `cc_shared_library`, `cc_binary`, `cc_import` and `cc_test` as built-in globals. Making the `load`s explicit is the correct practice regardless of Bazel version, and is a **prerequisite for the upcoming Bazel 9 bump** where those globals are removed entirely. Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>

### What does this PR do? Completes the full `rules_cc` migration started in #47716, covering the cases that were missed: our own .bzl rule files and the `gcc-toolchain` external dependency. ### Motivation #47716 covered `BUILD.bazel` files but left several `.bzl` files still relying on injected globals, absent from Bazel 9+. ### Additional Notes The additional patch to `gcc-toolchain` will disappear once f0rmiga/gcc-toolchain#217 gets merged.

### What does this PR do? Completes the full `rules_cc` migration started in #47716, covering the cases I missed: our own `.bzl` rule files and the `gcc-toolchain` external dependency. ### Motivation #47716 covered our `BUILD.bazel` files but left other files still relying on injected globals, absent from Bazel 9+. ### Additional Notes The additional patch to `gcc-toolchain` will disappear once f0rmiga/gcc-toolchain#217 gets merged. Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>

### What does this PR do? Upgrades the Bazel toolchain from 8.6.0 to 9.0.1. ### Motivation 9.0.1 ships two upstream fixes that directly benefit our build: - bazelbuild/bazel#28606: NPE when `--repo_env` is set to an env var that has no value — contributed by Datadog (Joseph Gette). - bazelbuild/bazel#26842: `DefaultSyscallCache` incorrectly treated `BUILD` files and `build` directories as the same entry on case-insensitive / normalizing filesystems (e.g. Linux container on a macOS host), causing spurious build failures. ### Describe how you validated your changes `bazel test //...` passes. ### Additional Notes Groundwork landed in advance: - #47716: Bump `rules_cc` with explicit loads for Bazel 9 - #47745: Fix `rules_cc` leftovers from #47716 for Bazel 9 - #47982: Add explicit `cc_static_library` import for Bazel 9 - #48016: Add explicit `py_binary` import for Bazel 9 - #48071: Bump `rules_foreign_cc` for Bazel 9 fixes - #48082: Bump `rules_python` to 1.9.0 and fix misuses spotted on Windows - #48183: Fix Python hermetic toolchain check for Bazel 9 - #48186: Disable `repo_contents_cache` when in-workspace for Bazel 9 - #48228: Bump `protobuf` Bazel dep to 34.1

@JSGette

### What does this PR do? Upgrade `bazel` from 8.6.0 to 9.0.1. ### Motivation Bazel 9.0.1 ships upstream fixes that directly benefit our build & developer experience: - bazelbuild/bazel#26842: `BUILD` files and `build` directories were incorrectly treated as the same entry on case-insensitive filesystems (e.g., Linux container running on a macOS host), causing spurious build failures (esp. for `rloader` we had to `gazelle`-exclude because of that), - bazelbuild/bazel#27695: a contribution of ours (also available in 8.6.0 as bazelbuild/bazel#28367) - nice to have when sharing a folder between a Linux host and a Windows VM through `virtiofs`, - bazelbuild/bazel#28640: another contribution of ours (@JSGette) - critical because it what preventing us from switching to Bazel 9 (ADMS config). ### Describe how you validated your changes `bazel test //...` passes. ### Additional Notes Groundwork landed in advance: - #47716 - #47745 - #47982 - #48016 - #48071 - #48082 - #48183 - #48186 - #48200 (>= Bazel 9 min) - #48201 (>= Bazel 9 min) - #48228 (>= Bazel 9 min) Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>

@JSGette

### What does this PR do? Upgrade `bazel` from 8.6.0 to 9.0.1. ### Motivation Bazel 9.0.1 ships upstream fixes that directly benefit our build & developer experience: - bazelbuild/bazel#26842: `BUILD` files and `build` directories were incorrectly treated as the same entry on case-insensitive filesystems (e.g., Linux container running on a macOS host), causing spurious build failures (esp. for `rloader` we had to `gazelle`-exclude because of that), - bazelbuild/bazel#27695: a contribution of ours (also available in 8.6.0 as bazelbuild/bazel#28367) - nice to have when sharing a folder between a Linux host and a Windows VM through `virtiofs`, - bazelbuild/bazel#28640: another contribution of ours (@JSGette) - critical because it what preventing us from switching to Bazel 9 (ADMS config). ### Describe how you validated your changes `bazel test //...` passes. ### Additional Notes Groundwork landed in advance: - #47716 - #47745 - #47982 - #48016 - #48071 - #48082 - #48183 - #48186 - #48200 (>= Bazel 9 min) - #48201 (>= Bazel 9 min) - #48228 (>= Bazel 9 min) Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>

@JSGette

### What does this PR do? Upgrade `bazel` from 8.6.0 to 9.0.1. ### Motivation Bazel 9.0.1 ships upstream fixes that directly benefit our build & developer experience: - bazelbuild/bazel#26842: `BUILD` files and `build` directories were incorrectly treated as the same entry on case-insensitive filesystems (e.g., Linux container running on a macOS host), causing spurious build failures (esp. for `rloader` we had to `gazelle`-exclude because of that), - bazelbuild/bazel#27695: a contribution of ours (also available in 8.6.0 as bazelbuild/bazel#28367) - nice to have when sharing a folder between a Linux host and a Windows VM through `virtiofs`, - bazelbuild/bazel#28640: another contribution of ours (@JSGette) - critical because it what preventing us from switching to Bazel 9 (ADMS config). ### Describe how you validated your changes `bazel test //...` passes. ### Additional Notes Groundwork landed in advance: - #47716 - #47745 - #47982 - #48016 - #48071 - #48082 - #48183 - #48186 - #48200 (>= Bazel 9 min) - #48201 (>= Bazel 9 min) - #48228 (>= Bazel 9 min) Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>

@JSGette

### What does this PR do? Upgrade `bazel` from 8.6.0 to 9.0.1. ### Motivation Bazel 9.0.1 ships upstream fixes that directly benefit our build & developer experience: - bazelbuild/bazel#26842: `BUILD` files and `build` directories were incorrectly treated as the same entry on case-insensitive filesystems (e.g., Linux container running on a macOS host), causing spurious build failures (esp. for `rloader` we had to `gazelle`-exclude because of that), - bazelbuild/bazel#27695: a contribution of ours (also available in 8.6.0 as bazelbuild/bazel#28367) - nice to have when sharing a folder between a Linux host and a Windows VM through `virtiofs`, - bazelbuild/bazel#28640: another contribution of ours (@JSGette) - critical because it what preventing us from switching to Bazel 9 (ADMS config). ### Describe how you validated your changes `bazel test //...` passes. ### Additional Notes Groundwork landed in advance: - #47716 - #47745 - #47982 - #48016 - #48071 - #48082 - #48183 - #48186 - #48200 (>= Bazel 9 min) - #48201 (>= Bazel 9 min) - #48228 (>= Bazel 9 min) Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>

rdesgroppes added the changelog/no-changelog No changelog entry needed label Mar 11, 2026

rdesgroppes requested a review from a team as a code owner March 11, 2026 12:36

rdesgroppes added the qa/no-code-change No code change in Agent code requiring validation label Mar 11, 2026

dd-octo-sts bot added internal Identify a non-fork PR team/agent-build labels Mar 11, 2026

github-actions bot added the long review PR is complex, plan time to review it label Mar 11, 2026

JSGette approved these changes Mar 11, 2026

View reviewed changes

rdesgroppes force-pushed the regis.desgroppes/prereq-rules-cc-explicit-loads branch from 107b445 to 524c447 Compare March 11, 2026 12:49

rdesgroppes force-pushed the regis.desgroppes/prereq-rules-cc-explicit-loads branch from 524c447 to 8d4f57c Compare March 11, 2026 12:53

gh-worker-dd-mergequeue-cf854d bot merged commit dbf2b24 into main Mar 11, 2026
267 checks passed

gh-worker-dd-mergequeue-cf854d bot deleted the regis.desgroppes/prereq-rules-cc-explicit-loads branch March 11, 2026 14:16

github-actions bot added this to the 7.78.0 milestone Mar 11, 2026

rdesgroppes mentioned this pull request Mar 11, 2026

Fix rules_cc leftovers from #47716 for Bazel 9 #47745

Merged

rdesgroppes mentioned this pull request Mar 23, 2026

Bump bazel to 9.0.1 #47742

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump `rules_cc` with explicit loads for Bazel 9#47716

Bump `rules_cc` with explicit loads for Bazel 9#47716
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit intomainfrom
regis.desgroppes/prereq-rules-cc-explicit-loads

rdesgroppes commented Mar 11, 2026

Uh oh!

agent-platform-auto-pr bot commented Mar 11, 2026

Uh oh!

agent-platform-auto-pr bot commented Mar 11, 2026

Uh oh!

rdesgroppes commented Mar 11, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Mar 11, 2026 •

edited

Loading

Uh oh!

cit-pr-commenter-54b7da bot commented Mar 11, 2026 •

edited

Loading

Experiments ignored for regressions

Fine details of change detection per experiment

Bounds Checks: ✅ Passed

Explanation

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

rdesgroppes commented Mar 11, 2026

What does this PR do?

Motivation

Uh oh!

agent-platform-auto-pr bot commented Mar 11, 2026

Files inventory check summary

Results for datadog-agent_7.78.0~devel.git.505.8d4f57c.pipeline.101848040-1_amd64.deb:

Uh oh!

agent-platform-auto-pr bot commented Mar 11, 2026

Static quality checks

Uh oh!

rdesgroppes commented Mar 11, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cit-pr-commenter-54b7da bot commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Regression Detector

Regression Detector Results

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Fine details of change detection per experiment

Bounds Checks: ✅ Passed

Explanation

CI Pass/Fail Decision

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

gh-worker-devflow-routing-ef8351 bot commented Mar 11, 2026 •

edited

Loading

cit-pr-commenter-54b7da bot commented Mar 11, 2026 •

edited

Loading