Bump Bazel to 9.2.0 for remote cache and Windows fixes

[rdesgroppes]

What does this PR do?

Bump the pinned Bazel version from 9.1.1 to 9.2.0 and refresh MODULE.bazel.lock accordingly.

Motivation

Bazel 9.2.0 ships fixes this repo has been working around over the past month.

Windows issues

Our contributions:

• [9.2.0] Fix launching executables whose path can't be shortened on Windows (https://github.com/bazelbuild/bazel/pull/29921) bazelbuild/bazel#29984, which should remove the need for temporary countermeasures we had to come up with:
  • [#incident-56436] Enable NTFS 8.3 short names in the Windows image datadog-agent-buildimages#1212 (alas ineffective),
  • [#incident-56436] Enable NTFS 8.3 short names at startup datadog-agent-buildimages#1215 (effective),
  • Fail bazel.bat early if 8.3 short names are disabled in Windows #52500,
• [9.2.0] Reland "Embed asInvoker UAC manifest in the Windows launcher stub" (https://github.com/bazelbuild/bazel/pull/30043) bazelbuild/bazel#30182, which should remove the need for:
  • Fix bazel run *install* for non-admin Windows users #52061,
  • chore(bazel): add --test_env=__COMPAT_LAYER=RunAsInvoker for Windows bazel test #53591.

Caching issues

• [9.2.0] Cache CAS interactions at lower layer to fix lost input handl… bazelbuild/bazel#29791,
• [9.2.0] Reupload in-memory blobs when inputs are force uploaded (https://github.com/bazelbuild/bazel/pull/29831) bazelbuild/bazel#29868,
• [9.2.0] Remove the client gRPC message size limit (https://github.com/bazelbu… bazelbuild/bazel#29885,
• [9.2.0] Recover lost inputs from deduplicated Merkle subtrees under path mapping bazelbuild/bazel#30193, a caveat mentioned in:
  • Enable Bazel action rewinding for Lost inputs no longer available remotely #53356.

Others

Also worth noting, though not tied to a specific incident here:

• [9.2.0] Ensure that transitive packages can be flattened efficiently (https://github.com/bazelbuild/bazel/pull/29800) bazelbuild/bazel#29807,
• [9.2.0] Enable TCP keepalive by default for gRPC connections. (https://github.com/bazelbuild/bazel/pull/29879) bazelbuild/bazel#29898,
• [9.2.0] Inject the repo env per-variable to avoid over-invalidation bazelbuild/bazel#30194.

Describe how you validated your changes

bazel version reports 9.2.0 after bazelisk re-bootstraps.
bazel build //pkg/config/schema/... completes successfully.
bazel shutdown followed by bazel mod deps --lockfile_mode=refresh leaves MODULE.bazel.lock unchanged.

Additional Notes

None of the .bazelrc UAC/8dot3 workarounds (DataDog/datadog-agent-buildimages#1215, #52500, #52061, #53591) are removed here.
Each needs its own re-verification on Windows before being reverted as follow-ups.

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 84c4b65e:

Results for datadog-agent_7.83.0~devel.git.86.d1c518c.pipeline.124468253-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

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

33 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	750.791 MiB
✅	agent_deb_amd64_fips	705.695 MiB
✅	agent_heroku_amd64	307.559 MiB
✅	agent_msi	645.449 MiB
✅	agent_rpm_amd64	750.774 MiB
✅	agent_rpm_amd64_fips	705.679 MiB
✅	agent_rpm_arm64	725.878 MiB
✅	agent_rpm_arm64_fips	684.464 MiB
✅	agent_suse_amd64	750.774 MiB
✅	agent_suse_amd64_fips	705.679 MiB
✅	agent_suse_arm64	725.878 MiB
✅	agent_suse_arm64_fips	684.464 MiB
✅	docker_agent_amd64	809.493 MiB
✅	docker_agent_arm64	809.606 MiB
✅	docker_agent_jmx_amd64	1000.391 MiB
✅	docker_agent_jmx_arm64	989.156 MiB
✅	docker_cluster_agent_amd64	209.877 MiB
✅	docker_cluster_agent_arm64	222.952 MiB
✅	docker_cws_instrumentation_amd64	7.447 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.204 MiB
✅	docker_dogstatsd_arm64	37.305 MiB
✅	docker_host_profiler_amd64	302.841 MiB
✅	docker_host_profiler_arm64	314.372 MiB
✅	dogstatsd_deb_amd64	29.939 MiB
✅	dogstatsd_deb_arm64	27.986 MiB
✅	dogstatsd_rpm_amd64	29.939 MiB
✅	dogstatsd_suse_amd64	29.939 MiB
✅	iot_agent_deb_amd64	46.187 MiB
✅	iot_agent_deb_arm64	42.878 MiB
✅	iot_agent_deb_armhf	43.643 MiB
✅	iot_agent_rpm_amd64	46.187 MiB
✅	iot_agent_suse_amd64	46.186 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 5b3c77f0-75c9-47e8-91fa-d7afa63a2428

Baseline: 0f59341
Comparison: 695123c
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+3.14	[+2.12, +4.16]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.41	[+0.35, +0.46]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	+0.13	[+0.04, +0.22]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	+0.05	[+0.01, +0.09]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.22	[-0.29, -0.15]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.34	[-0.40, -0.28]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.34	[-0.59, -0.10]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	146.43MiB ≤ 154MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	731.15KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	494.15MiB ≤ 495MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.12MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	184.05MiB ≤ 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.39MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	355.12 ≤ 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	393.74MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.94GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	38.53 ≤ 40	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	299.55MiB ≤ 330MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	74.42 ≤ 80	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	279.16MiB ≤ 310MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	35.56 ≤ 40	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	288.76MiB ≤ 320MiB	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".

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 Profiling Replicate Execution Failures (ddprof)

Note: Profiling replicas may still be executing. See the debug dashboard for up to date status.

Experiment	Variant	Replicates	Failure	Debug Dashboard
quality_gate_idle	baseline	10	Oom killed	Debug Dashboard
quality_gate_idle_all_features	baseline	10	Oom killed	Debug Dashboard
quality_gate_idle_all_features	comparison	10	Oom killed	Debug Dashboard
quality_gate_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_logs	comparison	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	comparison	10	Oom killed	Debug Dashboard
quality_gate_security_idle	baseline	10	Oom killed	Debug Dashboard
quality_gate_security_no_fs_load	baseline	10	Crashed (exit code: 134)	Debug Dashboard
quality_gate_security_no_fs_load	comparison	10	Oom killed	Debug Dashboard

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, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 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.
• quality_gate_metrics_logs, bounds check total_bytes_received: 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 cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, 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_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.

[temporal-github-worker-1]

Backport evaluation: View Slack thread

[dd-octo-sts]

⚠️ Automatic backport to 7.82.x failed.

This usually happens when the cherry-pick has merge conflicts and needs manual resolution.

To backport manually, run:

git fetch
git worktree add .worktrees/backport-7.82.x 7.82.x
cd .worktrees/backport-7.82.x
git switch --create backport-53619-to-7.82.x
git cherry-pick -x --mainline 1 695123cb8f59c89b370b6f1e6908ca02bf78144c
git push --set-upstream origin backport-53619-to-7.82.x

Workflow logs: https://github.com/DataDog/datadog-agent/actions/runs/32467791018