Bump `bazel` to 9.0.1 by rdesgroppes · Pull Request #47742 · DataDog/datadog-agent

rdesgroppes · 2026-03-11T20:00:37Z

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:

Fix DefaultSyscallCache for normalizing filesystems 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),
[9.0.0] Compensate for Windows filesystems lacking junction support bazelbuild/bazel#27695: a contribution of ours (also available in 8.6.0 as [8.6.0] Compensate for Windows filesystems lacking junction support bazelbuild/bazel#28367) - nice to have when sharing a folder between a Linux host and a Windows VM through virtiofs,
[9.0.1] Fix NPE caused by --repo_env with no value set (https://github.com/bazelbuild/bazel/pull/28606) 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:

agent-platform-auto-pr · 2026-03-18T13:39:46Z

Files inventory check summary

File checks results against ancestor 12849c7b:

Results for datadog-agent_7.79.0~devel.git.89.27a9a66.pipeline.104123592-1_amd64.deb:

No change detected

cit-pr-commenter-54b7da · 2026-03-18T14:02:14Z

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: d9ba776e-f1a0-4c1d-9103-e9c085ca87b3

Baseline: b188dde
Comparison: 8e3e8ce
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.12	[-2.92, +3.16]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_metrics_logs	memory utilization	+1.05	[+0.82, +1.29]	1	Logs bounds checks dashboard
➖	ddot_logs	memory utilization	+0.77	[+0.71, +0.84]	1	Logs
➖	docker_containers_memory	memory utilization	+0.69	[+0.59, +0.79]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	+0.69	[+0.55, +0.83]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.54	[+0.39, +0.70]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.19	[+0.13, +0.25]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.18	[+0.14, +0.21]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.17	[+0.12, +0.22]	1	Logs bounds checks dashboard
➖	docker_containers_cpu	% cpu utilization	+0.12	[-2.92, +3.16]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	+0.08	[-0.10, +0.25]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.02	[-0.41, +0.45]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.00	[-0.38, +0.38]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.19, +0.18]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.01	[-0.12, +0.11]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.01	[-0.20, +0.18]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.05	[-0.48, +0.38]	1	Logs
➖	file_tree	memory utilization	-0.06	[-0.11, -0.01]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.10	[-0.21, +0.02]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.21	[-0.43, +0.01]	1	Logs
➖	ddot_metrics	memory utilization	-0.26	[-0.43, -0.08]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.55	[-0.66, -0.44]	1	Logs
➖	quality_gate_logs	% cpu utilization	-2.73	[-4.27, -1.19]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	-2.87	[-2.99, -2.74]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	docker_containers_cpu	simple_check_run	10/10	733 ≥ 26
✅	docker_containers_memory	memory_usage	10/10	277.81MiB ≤ 370MiB
✅	docker_containers_memory	simple_check_run	10/10	710 ≥ 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	173.46MiB ≤ 175MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	2 ≤ 3	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	504.54MiB ≤ 550MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	206.50MiB ≤ 220MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	342.52 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	412.07MiB ≤ 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_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_metrics_logs, bounds check missed_bytes: 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 cpu_usage: 10/10 replicas passed. Gate passed.
quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.

agent-platform-auto-pr · 2026-03-19T01:23:19Z

Static quality checks

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

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	docker_agent_amd64	+2.14 KiB (0.00% increase)	813.107 → 813.109 → 815.700
✅	docker_agent_arm64	+4.34 KiB (0.00% increase)	816.230 → 816.234 → 821.970
✅	docker_agent_jmx_amd64	+2.16 KiB (0.00% increase)	1004.022 → 1004.024 → 1006.580
✅	docker_agent_jmx_arm64	+4.34 KiB (0.00% increase)	995.924 → 995.929 → 1001.570

27 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	752.798 MiB
✅	agent_deb_amd64_fips	709.754 MiB
✅	agent_heroku_amd64	313.153 MiB
✅	agent_msi	604.645 MiB
✅	agent_rpm_amd64	752.782 MiB
✅	agent_rpm_amd64_fips	709.738 MiB
✅	agent_rpm_arm64	731.146 MiB
✅	agent_rpm_arm64_fips	691.134 MiB
✅	agent_suse_amd64	752.782 MiB
✅	agent_suse_amd64_fips	709.738 MiB
✅	agent_suse_arm64	731.146 MiB
✅	agent_suse_arm64_fips	691.134 MiB
✅	docker_cluster_agent_amd64	205.320 MiB
✅	docker_cluster_agent_arm64	219.677 MiB
✅	docker_cws_instrumentation_amd64	7.142 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	39.230 MiB
✅	docker_dogstatsd_arm64	37.445 MiB
✅	dogstatsd_deb_amd64	29.874 MiB
✅	dogstatsd_deb_arm64	28.026 MiB
✅	dogstatsd_rpm_amd64	29.874 MiB
✅	dogstatsd_suse_amd64	29.874 MiB
✅	iot_agent_deb_amd64	43.262 MiB
✅	iot_agent_deb_arm64	40.309 MiB
✅	iot_agent_deb_armhf	41.052 MiB
✅	iot_agent_rpm_amd64	43.262 MiB
✅	iot_agent_suse_amd64	43.262 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+19.28 KiB (0.01% increase)	174.813 → 174.832 → 178.360
✅	agent_deb_amd64_fips	-50.12 KiB (0.03% reduction)	165.416 → 165.367 → 172.790
✅	agent_heroku_amd64	+5.58 KiB (0.01% increase)	74.979 → 74.985 → 79.970
✅	agent_msi	-16.0 KiB (0.01% reduction)	138.324 → 138.309 → 146.220
✅	agent_rpm_amd64	-35.63 KiB (0.02% reduction)	177.697 → 177.662 → 181.830
✅	agent_rpm_amd64_fips	-18.06 KiB (0.01% reduction)	167.683 → 167.666 → 173.370
✅	agent_rpm_arm64	+5.83 KiB (0.00% increase)	159.636 → 159.642 → 163.060
✅	agent_rpm_arm64_fips	+6.09 KiB (0.00% increase)	151.466 → 151.472 → 156.170
✅	agent_suse_amd64	-35.63 KiB (0.02% reduction)	177.697 → 177.662 → 181.830
✅	agent_suse_amd64_fips	-18.06 KiB (0.01% reduction)	167.683 → 167.666 → 173.370
✅	agent_suse_arm64	+5.83 KiB (0.00% increase)	159.636 → 159.642 → 163.060
✅	agent_suse_arm64_fips	+6.09 KiB (0.00% increase)	151.466 → 151.472 → 156.170
✅	docker_agent_amd64	neutral	268.255 MiB → 272.480
✅	docker_agent_arm64	+6.14 KiB (0.00% increase)	255.450 → 255.456 → 261.060
✅	docker_agent_jmx_amd64	+6.18 KiB (0.00% increase)	336.902 → 336.908 → 341.100
✅	docker_agent_jmx_arm64	+9.93 KiB (0.00% increase)	320.077 → 320.087 → 325.620
✅	docker_cluster_agent_amd64	neutral	71.934 MiB → 72.920
✅	docker_cluster_agent_arm64	neutral	67.502 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.169 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.490 MiB → 14.830
✅	dogstatsd_deb_amd64	+2.38 KiB (0.03% increase)	7.889 → 7.891 → 8.790
✅	dogstatsd_deb_arm64	neutral	6.775 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.901 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.901 MiB → 8.800
✅	iot_agent_deb_amd64	+3.1 KiB (0.03% increase)	11.394 → 11.397 → 12.040
✅	iot_agent_deb_arm64	-2.09 KiB (0.02% reduction)	9.700 → 9.697 → 10.450
✅	iot_agent_deb_armhf	+2.15 KiB (0.02% increase)	9.934 → 9.936 → 10.620
✅	iot_agent_rpm_amd64	neutral	11.412 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.412 MiB → 12.060

### 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

Now lifted by #47742.

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

### What does this PR do? Configure the `//:gazelle` target with `-build_file_name=BUILD.bazel`. ### Motivation When `gazelle` runs inside a Linux container on macOS via Docker Desktop, the workspace is typically mounted on a case-insensitive filesystem where `BUILD` and `build` are indistinguishable. This causes spurious errors such as: ```sh bazel run //:gazelle; echo $? ... gazelle: open /dda/.gitlab/windows/build: no such file or directory open /dda/rtloader/build: no such file or directory 1 ``` Whereas the cause strictly resides in a filesystem layer/driver (docker/desktop-feedback#251, recently imported from docker/for-mac#7218), portable tools have been taking countermeasures. Bazel 9, for instance, revamped their filesystem cache to better accomodate case-insensitive filesystems (bazelbuild/bazel#26842), which led us to switch to it (#47742), but that only covers Bazel's own I/O, not the processes it spawns, of which `gazelle`. For that purpose, Gazelle happens to explicitly recommend setting its `build_file_name` directive to `BUILD.bazel`: > If a repository contains files named `build` that aren't related to Bazel, it may help to set this to `"BUILD.bazel"`, especially on case-insensitive file systems. ### Additional Notes For consistency with the narrowed scope, this change renames `compliance/rules/BUILD` to `compliance/rules/BUILD.bazel` (the only plain `BUILD` file still present in the tree).

### What does this PR do? Configure the `//:gazelle` target with `-build_file_name=BUILD.bazel`. ### Motivation When `gazelle` runs inside a Linux container on macOS via Docker Desktop, the workspace is typically mounted on a case-insensitive filesystem where `BUILD` and `build` are indistinguishable. This causes spurious errors such as: ```sh bazel run //:gazelle; echo $? ... gazelle: open /dda/.gitlab/windows/build: no such file or directory open /dda/rtloader/build: no such file or directory 1 ``` Whereas the cause strictly resides in a filesystem layer/driver (docker/desktop-feedback#251, recently imported from docker/for-mac#7218), portable tools have been taking countermeasures. Bazel 9, for instance, revamped their filesystem cache to better accomodate case-insensitive filesystems (bazelbuild/bazel#26842), which led us to switch to it (#47742), but that only covers Bazel's own I/O, not the processes it spawns, of which `gazelle`. For that purpose, Gazelle happens to [explicitly recommend](https://github.com/bazel-contrib/bazel-gazelle/blob/4a7caee10fbd2da9bb059f3ce7c2cac8d0050e53/reference.md?plain=1#L251) setting its `build_file_name` directive to `BUILD.bazel`: > If a repository contains files named `build` that aren't related to Bazel, it may help to set this to `"BUILD.bazel"`, especially on case-insensitive file systems. ### Additional Notes For consistency with the narrowed scope, this change renames `compliance/rules/BUILD` to `compliance/rules/BUILD.bazel` (the only plain `BUILD` file still present in the tree). 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 changelog/no-changelog No changelog entry needed qa/no-code-change No code change in Agent code requiring validation labels Mar 11, 2026

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

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

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch 3 times, most recently from a272687 to f86af5a Compare March 12, 2026 16:47

github-actions bot added medium review PR review might take time and removed long review PR is complex, plan time to review it labels Mar 12, 2026

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch from f86af5a to 68fe95d Compare March 12, 2026 17:38

github-actions bot added long review PR is complex, plan time to review it and removed medium review PR review might take time labels Mar 12, 2026

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch 4 times, most recently from 00063ed to a99bea1 Compare March 13, 2026 12:09

github-actions bot added medium review PR review might take time and removed long review PR is complex, plan time to review it labels Mar 13, 2026

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch 2 times, most recently from 8dfda2f to 2c4edf3 Compare March 18, 2026 12:27

github-actions bot added long review PR is complex, plan time to review it and removed medium review PR review might take time labels Mar 18, 2026

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch from 2c4edf3 to d603c29 Compare March 18, 2026 12:59

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch 3 times, most recently from 53c8232 to eae266a Compare March 19, 2026 00:31

github-actions bot added medium review PR review might take time and removed long review PR is complex, plan time to review it labels Mar 21, 2026

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch 7 times, most recently from c877e8e to 07cb688 Compare March 23, 2026 17:09

github-actions bot added long review PR is complex, plan time to review it and removed medium review PR review might take time labels Mar 23, 2026

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch from 07cb688 to cd831b4 Compare March 23, 2026 20:44

github-actions bot added medium review PR review might take time and removed long review PR is complex, plan time to review it labels Mar 23, 2026

rdesgroppes marked this pull request as ready for review March 23, 2026 21:01

rdesgroppes requested a review from a team as a code owner March 23, 2026 21:01

rdesgroppes force-pushed the regis.desgroppes/bazel-9 branch from cd831b4 to 27a9a66 Compare March 24, 2026 07:44

JSGette approved these changes Mar 24, 2026

View reviewed changes

gh-worker-dd-mergequeue-cf854d bot merged commit 8e3e8ce into main Mar 24, 2026
255 checks passed

gh-worker-dd-mergequeue-cf854d bot deleted the regis.desgroppes/bazel-9 branch March 24, 2026 09:14

github-actions bot added this to the 7.79.0 milestone Mar 24, 2026

rdesgroppes added a commit that referenced this pull request Mar 24, 2026

Remove gazelle:excludes awaiting Bazel 9

f0c6115

Now lifted by #47742.

rdesgroppes mentioned this pull request Mar 24, 2026

Remove redundant gazelle exclusions (**/build) and fix setup inconsistencies #48279

Merged

rdesgroppes mentioned this pull request Mar 26, 2026

Make gazelle consider only BUILD.bazel files #48455

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump `bazel` to 9.0.1#47742

Bump `bazel` to 9.0.1#47742
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit intomainfrom
regis.desgroppes/bazel-9

rdesgroppes commented Mar 11, 2026 •

edited

Loading

Uh oh!

agent-platform-auto-pr bot commented Mar 18, 2026 •

edited

Loading

Uh oh!

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

edited

Loading

Experiments ignored for regressions

Fine details of change detection per experiment

Bounds Checks: ✅ Passed

Explanation

Uh oh!

agent-platform-auto-pr bot commented Mar 19, 2026 •

edited

Loading

Info

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

rdesgroppes commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

Uh oh!

agent-platform-auto-pr bot commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Files inventory check summary

Results for datadog-agent_7.79.0~devel.git.89.27a9a66.pipeline.104123592-1_amd64.deb:

Uh oh!

cit-pr-commenter-54b7da bot commented Mar 18, 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!

agent-platform-auto-pr bot commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Static quality checks

Info

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

rdesgroppes commented Mar 11, 2026 •

edited

Loading

agent-platform-auto-pr bot commented Mar 18, 2026 •

edited

Loading

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

edited

Loading

agent-platform-auto-pr bot commented Mar 19, 2026 •

edited

Loading