native_test + py_binary + Windows

[tpudlik]

🐞 bug report

Affected Rule

The issue is caused by the rule: py_binary

Is this a regression?

I don't believe so, although native_test was introduced specifically to support Windows (bazelbuild/bazel-skylib#148), so it's surprising that it fails on this OS.

Description

Attempting to run a native_test wrapping a py_binary on Windows produces errors.

🔬 Minimal Reproduction

#2516 introduced a new test in examples/bzlmod, //py_proto_library:external_import_test. This test is marked incompatible with Windows (via target_compatible_with) because it fails on Windows.

🔥 Exception or Error

https://buildkite.com/bazel/rules-python-python/builds/10080#0193e584-8c2e-4cf4-8c53-9f339641422d

C:/b/7bjinhbd/external/rules_python~~python~python_3_9_x86_64-pc-windows-msvc/python.exe: can't open file 'C:\b\7bjinhbd\execroot\_main\bazel-out\x64_windows-fastbuild\bin\py_proto_library\external_import_test.exe.runfiles\_main\py_proto_library\external_import_test.zip': [Errno 2] No such file or directory

[rickeylev]

Thanks for the repro. This error looks familiar to a weird bug report I saw filed against the builtin rules in bazel. So maybe this repro at least lets us figure out what the cause is.

The thing that comes to mind is: I seem to recall that the windows bootstrap expects, given blaze-bin/foo that there is a sibling file (i.e. bazel-bin/foo or bazel-bin/foo.zip depending on whether zip-builds are enabled or not (default true for windows)) to exist. Being as how native_test symlinks to the original executable, I wouldn't be surprised if that assumption doesn't hold.