From 48eaaf3de8f5c94dc79872dcf7110ffc0ad24e5c Mon Sep 17 00:00:00 2001
From: "datadog-datadog-prod-us1-2[bot]"
 <261164178+datadog-datadog-prod-us1-2[bot]@users.noreply.github.com>
Date: Mon, 23 Mar 2026 12:04:22 +0000
Subject: [PATCH] =?UTF-8?q?Revert=20"Work=20around=20intermittent=20Window?=
 =?UTF-8?q?s=20build=20failure=20(missing=20pyconfig.h.=20e=E2=80=A6"?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This reverts commit f9026689bca5ac06e10eba4e9c72f71ed62f71ac.
---
 .bazelrc | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/.bazelrc b/.bazelrc
index 38f3bfdbd07926..33c29b363f74a0 100644
--- a/.bazelrc
+++ b/.bazelrc
@@ -41,12 +41,6 @@ common:macos --remote_local_fallback_strategy=sandboxed
 
 # Windows config -------------------------------------------------------------------------------------------------------
 common:windows --strategy=standalone # Valid values are: [dynamic_worker, standalone, dynamic, remote, worker, local]
-# TODO(agent-build): rules_python 1.9.0 transitions py_binary to enable_runfiles=true on Windows, creating a second
-# Bazel configuration. build_python.bat writes PCbuild/ intermediate files into the shared execroot source tree, so two
-# concurrent builds of python_win (one per configuration) race on those files. Setting enable_runfiles globally makes
-# the transition a no-op (same flag value => same config hash => one build). The proper fix is to make build_python.bat
-# hermetic by redirecting MSBuild's OutDir and intermediate paths to $(@D) instead of the source tree.
-common:windows --enable_runfiles
 # Neither repo_env nor shell_executable affect action keys. It can be both an advantage and a disadvantage.
 # For instance, if we need to have some special behavior in bash we can add it, however, in some cases
 # it may lead to cache poisoning.