Fix Python hermetic toolchain check for Bazel 9 by rdesgroppes · Pull Request #48183 · DataDog/datadog-agent

rdesgroppes · 2026-03-23T07:05:19Z

What does this PR do?

Fix //bazel/tests:does_python_work for Bazel 9 compatibility.

Motivation

Since Bazel 9, external repository contents are stored in a Content-Addressable Store (CAS) under cache/repos/v1/contents/<hash>/... instead of the human-readable named path under external/.

os.path.realpath(sys.executable) now resolves to the CAS path, which no longer contains rules_python, so the assertion fails:

  AssertionError: Regex didn't match: 'rules_python.+x86_64.+linux'
  not found in
  '.../cache/repos/v1/contents/e0e23621.../bin/python3.12' :
  python must come from hermetic toolchain instead of host!

Actual stdlib install paths are unaffected.

Describe how you validated your changes

bazel test //bazel/tests:does_python_work passes.

### What does this PR do? Fix `//bazel/tests:does_python_work` for Bazel 9 compatibility. ### Motivation In Bazel 9, external repository contents are stored in a Content-Addressable Store (CAS) under cache/repos/v1/contents/<hash>/... instead of the human-readable named path under external/. `os.path.realpath(sys.executable)` now resolves to the CAS path, which no longer contains `rules_python`, so the assertion fails: ``` AssertionError: Regex didn't match: 'rules_python.+x86_64.+linux' not found in '.../cache/repos/v1/contents/e0e23621.../bin/python3.12' : python must come from hermetic toolchain instead of host! ``` `sysconfig.get_path('stdlib')` is unaffected: it is computed from the Python installation prefix recorded in `sysconfig`, which still points to the named symlink tree under execroot that contains `rules_python`. ### Describe how you validated your changes `bazel test //bazel/tests:does_python_work` passes.

agent-platform-auto-pr · 2026-03-23T07:33:25Z

Files inventory check summary

File checks results against ancestor 6ffeeecb:

Results for datadog-agent_7.79.0~devel.git.43.1e7f3ce.pipeline.103930060-1_amd64.deb:

No change detected

agent-platform-auto-pr · 2026-03-23T07:54:04Z

Static quality checks

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

31 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	751.536 MiB
✅	agent_deb_amd64_fips	708.503 MiB
✅	agent_heroku_amd64	313.045 MiB
✅	agent_msi	604.516 MiB
✅	agent_rpm_amd64	751.520 MiB
✅	agent_rpm_amd64_fips	708.487 MiB
✅	agent_rpm_arm64	729.873 MiB
✅	agent_rpm_arm64_fips	689.849 MiB
✅	agent_suse_amd64	751.520 MiB
✅	agent_suse_amd64_fips	708.487 MiB
✅	agent_suse_arm64	729.873 MiB
✅	agent_suse_arm64_fips	689.849 MiB
✅	docker_agent_amd64	811.843 MiB
✅	docker_agent_arm64	814.959 MiB
✅	docker_agent_jmx_amd64	1002.759 MiB
✅	docker_agent_jmx_arm64	994.653 MiB
✅	docker_cluster_agent_amd64	205.316 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.254 MiB
✅	iot_agent_deb_arm64	40.305 MiB
✅	iot_agent_deb_armhf	41.052 MiB
✅	iot_agent_rpm_amd64	43.255 MiB
✅	iot_agent_suse_amd64	43.255 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+22.28 KiB (0.01% increase)	174.741 → 174.763 → 178.360
✅	agent_deb_amd64_fips	+29.99 KiB (0.02% increase)	165.343 → 165.372 → 172.790
✅	agent_heroku_amd64	neutral	74.960 MiB → 79.970
✅	agent_msi	+4.0 KiB (0.00% increase)	138.191 → 138.195 → 146.220
✅	agent_rpm_amd64	-46.56 KiB (0.03% reduction)	177.632 → 177.586 → 181.830
✅	agent_rpm_amd64_fips	-6.77 KiB (0.00% reduction)	167.608 → 167.601 → 173.370
✅	agent_rpm_arm64	-6.42 KiB (0.00% reduction)	159.569 → 159.563 → 163.060
✅	agent_rpm_arm64_fips	+23.35 KiB (0.02% increase)	151.388 → 151.410 → 156.170
✅	agent_suse_amd64	-46.56 KiB (0.03% reduction)	177.632 → 177.586 → 181.830
✅	agent_suse_amd64_fips	-6.77 KiB (0.00% reduction)	167.608 → 167.601 → 173.370
✅	agent_suse_arm64	-6.42 KiB (0.00% reduction)	159.569 → 159.563 → 163.060
✅	agent_suse_arm64_fips	+23.35 KiB (0.02% increase)	151.388 → 151.410 → 156.170
✅	docker_agent_amd64	+2.97 KiB (0.00% increase)	268.116 → 268.118 → 272.480
✅	docker_agent_arm64	-4.0 KiB (0.00% reduction)	255.319 → 255.315 → 261.060
✅	docker_agent_jmx_amd64	neutral	336.770 MiB → 341.100
✅	docker_agent_jmx_arm64	-6.14 KiB (0.00% reduction)	319.961 → 319.955 → 325.620
✅	docker_cluster_agent_amd64	neutral	71.931 MiB → 72.920
✅	docker_cluster_agent_arm64	neutral	67.505 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.488 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.891 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.775 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.900 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.900 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.396 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.699 MiB → 10.450
✅	iot_agent_deb_armhf	neutral	9.935 MiB → 10.620
✅	iot_agent_rpm_amd64	neutral	11.414 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.414 MiB → 12.060

cit-pr-commenter-54b7da · 2026-03-23T07:56:53Z

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: e374bc80-2f91-4b26-bea3-4f0b10cb68df

Baseline: 919d6b2
Comparison: c1d67a9
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	+1.50	[-1.58, +4.58]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+1.50	[-1.58, +4.58]	1	Logs
➖	quality_gate_logs	% cpu utilization	+1.27	[-0.36, +2.90]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	+1.16	[+0.92, +1.40]	1	Logs bounds checks dashboard
➖	otlp_ingest_metrics	memory utilization	+0.36	[+0.20, +0.51]	1	Logs
➖	quality_gate_idle	memory utilization	+0.10	[+0.05, +0.15]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.10	[-0.33, +0.53]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.04	[-0.43, +0.52]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.01	[-0.19, +0.21]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.10, +0.11]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.21, +0.19]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.03	[-0.42, +0.36]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.07	[-0.15, +0.01]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.10	[-0.32, +0.13]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.12	[-0.18, -0.07]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.19	[-0.23, -0.15]	1	Logs bounds checks dashboard
➖	docker_containers_memory	memory utilization	-0.27	[-0.34, -0.20]	1	Logs
➖	ddot_metrics	memory utilization	-0.29	[-0.47, -0.11]	1	Logs
➖	ddot_logs	memory utilization	-0.32	[-0.37, -0.26]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	-0.33	[-0.50, -0.17]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.35	[-0.47, -0.22]	1	Logs
➖	file_tree	memory utilization	-0.35	[-0.41, -0.30]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.36	[-0.44, -0.27]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.38	[-0.52, -0.24]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	docker_containers_cpu	simple_check_run	10/10	711 ≥ 26
✅	docker_containers_memory	memory_usage	10/10	273.19MiB ≤ 370MiB
✅	docker_containers_memory	simple_check_run	10/10	728 ≥ 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.88MiB ≤ 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	492.68MiB ≤ 550MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	203.46MiB ≤ 220MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	371.46 ≤ 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	409.92MiB ≤ 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_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate 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_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 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 cpu_usage: 10/10 replicas passed. Gate passed.
quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.

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

### What does this PR do? Fix `//bazel/tests:does_python_work` for Bazel 9 compatibility. ### Motivation Since Bazel 9, external repository contents are stored in a Content-Addressable Store (CAS) under `cache/repos/v1/contents/<hash>/...` instead of the human-readable named path under `external/`. `os.path.realpath(sys.executable)` now resolves to the CAS path, which no longer contains `rules_python`, so the assertion fails: ``` AssertionError: Regex didn't match: 'rules_python.+x86_64.+linux' not found in '.../cache/repos/v1/contents/e0e23621.../bin/python3.12' : python must come from hermetic toolchain instead of host! ``` Actual stdlib install paths are unaffected. ### Describe how you validated your changes `bazel test //bazel/tests:does_python_work` passes. 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>

### What does this PR do? Fix `//bazel/tests:does_python_work` for Bazel 9 compatibility. ### Motivation Since Bazel 9, external repository contents are stored in a Content-Addressable Store (CAS) under `cache/repos/v1/contents/<hash>/...` instead of the human-readable named path under `external/`. `os.path.realpath(sys.executable)` now resolves to the CAS path, which no longer contains `rules_python`, so the assertion fails: ``` AssertionError: Regex didn't match: 'rules_python.+x86_64.+linux' not found in '.../cache/repos/v1/contents/e0e23621.../bin/python3.12' : python must come from hermetic toolchain instead of host! ``` Actual stdlib install paths are unaffected. ### Describe how you validated your changes `bazel test //bazel/tests:does_python_work` passes. 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 23, 2026

rdesgroppes requested a review from a team as a code owner March 23, 2026 07:05

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

github-actions bot added the short review PR is simple enough to be reviewed quickly label Mar 23, 2026

rdesgroppes force-pushed the regis.desgroppes/fix-python-test-for-bazel-9 branch from 1f717f4 to 1e7f3ce Compare March 23, 2026 07:11

rdesgroppes changed the title ~~Fix Python hermetic-toolchain check for Bazel 9~~ Fix Python hermetic toolchain check for Bazel 9 Mar 23, 2026

JSGette approved these changes Mar 23, 2026

View reviewed changes

gh-worker-dd-mergequeue-cf854d bot merged commit c1d67a9 into main Mar 23, 2026
258 checks passed

gh-worker-dd-mergequeue-cf854d bot deleted the regis.desgroppes/fix-python-test-for-bazel-9 branch March 23, 2026 10:06

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

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

Fix Python hermetic toolchain check for Bazel 9#48183

Fix Python hermetic toolchain check for Bazel 9#48183
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit intomainfrom
regis.desgroppes/fix-python-test-for-bazel-9

rdesgroppes commented Mar 23, 2026 •

edited

Loading

Uh oh!

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

Uh oh!

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

Uh oh!

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

Uh oh!

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

Files inventory check summary

Results for datadog-agent_7.79.0~devel.git.43.1e7f3ce.pipeline.103930060-1_amd64.deb:

Uh oh!

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

Static quality checks

Uh oh!

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

rdesgroppes commented Mar 23, 2026 •

edited

Loading

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

edited

Loading