On Windows, bazel test uses a different PATH value than bazel build, which results in duplicated build steps. Since bazel test //... also builds all targets, the additional build step does not provide additional assurances.
This may also resolve failed to delete output files errors which occur during the test step, likely because the build step leaks open files somewhere.
On Windows,
bazel testuses a differentPATHvalue thanbazel build, which results in duplicated build steps. Sincebazel test //...also builds all targets, the additionalbuildstep does not provide additional assurances.This may also resolve
failed to delete output fileserrors which occur during the test step, likely because the build step leaks open files somewhere.