-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BAZEL_TEST env variable is not sent on Windows #21420
Comments
This was added in #15393, which simply missed the case of Windows. Would you be interested in submitting a PR? You would need to add a bazel/tools/test/windows/tw.cc Line 1933 in 4e43b4a
|
This was an oversight from when exporting BAZEL_TEST on Linux. fixes: bazelbuild#21420
@bazel-io fork 7.1.0 |
This was an oversight from when exporting BAZEL_TEST on Linux. fixes: bazelbuild#21420 Closes bazelbuild#21444. PiperOrigin-RevId: 610338496 Change-Id: Icbbdc42b6ea92a2de2b0c558aea47a24493c9d8a
A fix for this issue has been included in Bazel 7.1.0 RC2. Please test out the release candidate and report any issues as soon as possible. |
Used bazelisk with |
Description of the bug:
According to https://bazel.build/reference/test-encyclopedia#initial-conditions, the
BAZEL_TEST
environment variable is sent to the underlying program to mark is as being run by bazel test. This works on Linux, but on Windows that environment variable is not sent.Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Wrote the following test on linux, which passes:
But the equivalent test on Windows does not pass:
Which operating system are you running Bazel on?
Windows and Linux
What is the output of
bazel info release
?Windows & Linux: release 7.0.2 (via Bazelisk)
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
I did google for this, but could not find any relevant information. If there is a known issue, I apologize for not finding it.
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: