Handle empty environment variables in Windows test wrapper. In Bazel's Windows test wrapper, passing an empty environment variable (such as `--action_env=PATH=`) caused `GetEnv` to fail. The Win32 `GetEnvironmentVariableW` function returns 0 with `GetLastError() == 0` (`ERROR_SUCCESS`) for defined empty variables, but the wrapper only checked for `ERROR_ENVVAR_NOT_FOUND`, misidentifying empty variables as read errors. Furthermore, stale thread error codes from prior operations could lead to false failures. Clear `GetLastError()` via `SetLastError(0)` before calling `GetEnvironmentVariableW`, and treat both `0` (`ERROR_SUCCESS`) and `ERROR_ENVVAR_NOT_FOUND` as valid empty-variable outcomes when the returned character count is 0. Fixes https://github.com/bazelbuild/bazel/issues/15364 RELNOTES: Fix an issue on Windows where empty environment variables (e.g. `--action_env=VAR=`) caused test execution failures in the test wrapper. PiperOrigin-RevId: 971824558 Change-Id: I0eb1fff4d03db0faa57d52a3729a179f9cc8509d
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
