You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently rust_test targets use a custom test launcher to configure environment variables for use during tests. In #960 a change was made to switch tests to use Bazel's testing.TestEnvironment provider. This solves for situations where using --run_under resulted in inconsistent behavior as the binary being run was not the expected test executable but the custom test launcher. As of now the custom test launcher is only used when execpath is used in a rust_test.env value as the launcher expands execpath variables to absolute paths, where the TestEnvironment variable does not. In many cases, this change in behavior can be worked around in code where issues with --run_under could not. This flag tracks the deprecation of the custom test launcher in rules_rust.
The text was updated successfully, but these errors were encountered:
Currently
rust_test
targets use a custom test launcher to configure environment variables for use during tests. In #960 a change was made to switch tests to use Bazel's testing.TestEnvironment provider. This solves for situations where using --run_under resulted in inconsistent behavior as the binary being run was not the expected test executable but the custom test launcher. As of now the custom test launcher is only used whenexecpath
is used in arust_test.env
value as the launcher expandsexecpath
variables to absolute paths, where theTestEnvironment
variable does not. In many cases, this change in behavior can be worked around in code where issues with--run_under
could not. This flag tracks the deprecation of the custom test launcher inrules_rust
.The text was updated successfully, but these errors were encountered: