Skip to content
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

Windows: add --incompatible_windows_native_test_wrapper #7644

Closed

Conversation

laszlocsomor
Copy link
Contributor

Add the --incompatible_windows_native_test_wrapper
flag (default: false). This flag has no effect on
platforms other than Windows.

When using bazel test, Bazel does not execute
tests directly. Instead Bazel runs a "test
wrapper" as a subprocess, which sets up the
environment for the test and runs the test.

By default, Bazel uses a Bash script
(@bazel_tools//tools/test:test-setup.sh) as the
test wrapper, on all platforms. The new flag
allows using an alternative test wrapper written
in C++ that does not depend on Bash.

Flag semantics:

  • When true: Bazel uses the C++ test wrapper from
    @bazel_tools//tools/test:tw. This test wrapper
    does not depend on Bash.
  • When false: Bazel uses the Bash script test
    wrapper also used on every other platform, from
    @bazel_tools//tools/test:test-setup.sh. This
    script requires Bash.

Incompatible flag: #6622

Related: #5508

RELNOTES[NEW]: Added --incompatible_windows_native_test_wrapper flag: enables using the Bash-less test wrapper on Windows. (No-op on other platforms.)

Add the --incompatible_windows_native_test_wrapper
flag (default: false). This flag has no effect on
platforms other than Windows.

When using `bazel test`, Bazel does not execute
tests directly. Instead Bazel runs a "test
wrapper" as a subprocess, which sets up the
environment for the test and runs the test.

By default, Bazel uses a Bash script
(`@bazel_tools//tools/test:test-setup.sh`) as the
test wrapper, on all platforms. The new flag
allows using an alternative test wrapper written
in C++ that does not depend on Bash.

Flag semantics:
- When true: Bazel uses the C++ test wrapper from
  `@bazel_tools//tools/test:tw`. This test wrapper
  does not depend on Bash.
- When false: Bazel uses the Bash script test
  wrapper also used on every other platform, from
  `@bazel_tools//tools/test:test-setup.sh`. This
  script requires Bash.

Incompatible flag: bazelbuild#6622

Related: bazelbuild#5508

RELNOTES[NEW]: Added --incompatible_windows_native_test_wrapper flag: enables using the Bash-less test wrapper on Windows. (No-op on other platforms.)
@bazel-io bazel-io closed this in ea4829a Mar 7, 2019
@laszlocsomor laszlocsomor deleted the tw-incompat-flag branch March 7, 2019 09:35
laszlocsomor added a commit that referenced this pull request Mar 7, 2019
Add the --incompatible_windows_native_test_wrapper
flag (default: false). This flag has no effect on
platforms other than Windows.

When using `bazel test`, Bazel does not execute
tests directly. Instead Bazel runs a "test
wrapper" as a subprocess, which sets up the
environment for the test and runs the test.

By default, Bazel uses a Bash script
(`@bazel_tools//tools/test:test-setup.sh`) as the
test wrapper, on all platforms. The new flag
allows using an alternative test wrapper written
in C++ that does not depend on Bash.

Flag semantics:
- When true: Bazel uses the C++ test wrapper from
  `@bazel_tools//tools/test:tw`. This test wrapper
  does not depend on Bash.
- When false: Bazel uses the Bash script test
  wrapper also used on every other platform, from
  `@bazel_tools//tools/test:test-setup.sh`. This
  script requires Bash.

Incompatible flag: #6622

Related: #5508

RELNOTES[NEW]: Added --incompatible_windows_native_test_wrapper flag: enables using the Bash-less test wrapper on Windows. (No-op on other platforms.)

Closes #7644.

PiperOrigin-RevId: 237201616
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants