bazel-contrib / bazel-contrib/rules_python
Wrapping py_binary
- Langage dominant
- Starlark
- Étoiles
- 688
- Forks
- 721
- Merge moyen
- 15 h 7 min
- PR mergées (30 j)
- 76
Description
Bazel test for wrapping binaries fails on py_binary with rules_python 0.36.0 on Windows.
To reproduce run `bazel test //src/test/py/bazel:runfiles_test` on Windows (with the test enabled).
Error output:
```
$TEST_TMPDIR defined: output root default is 'c:\b\n444gjid\execroot\_main\_tmp\a2d17f8b6d1ffa17ed8c03a73e21ab9e' and max_idle_secs default is '15'.
Starting local Bazel server and connecting to it...
Computing main repo mapping:
Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
Analyzing: target //wrapped:wrapped (1 packages loaded, 0 targets configured)
Analyzing: target //wrapped:wrapped (1 packages loaded, 0 targets configured)
Analyzing: target //wrapped:wrapped (52 packages loaded, 300 targets configured)
Analyzing: target //wrapped:wrapped (52 packages loaded, 300 targets configured)
Analyzing: target //wrapped:wrapped (58 packages loaded, 325 targets configured)
INFO: Analyzed target //wrapped:wrapped (61 packages loaded, 3435 targets configured).
[8 / 9] Building Python zip: //:binary; 0s local
INFO: Found 1 target...
Target //wrapped:wrapped up-to-date:
bazel-bin/binary.zip
bazel-bin/binary.exe
INFO: Elapsed time: 17.678s, Critical Path: 7.79s
INFO: 9 processes: 7 internal, 2 local.
INFO: Build completed successfully, 9 total actions
INFO: Running command line: bazel-bin/wrapped/binary.exe
C:/b/n444gjid/execroot/_main/_tmp/a2d17f8b6d1ffa17ed8c03a73e21ab9e/_bazel_b/5ca6k2uw/external/rules_python++python+python_3_11_x86_64-pc-windows-msvc/python.exe: can't open file 'C:\\b\\n444gjid\\execroot\\_main\\_tmp\\a2d17f8b6d1ffa17ed8c03a73e21ab9e\\_bazel_b\\5ca6k2uw\\execroot\\_main\\bazel-out\\x64_windows-fastbuild\\bin\\wrapped\\binary.zip': [Errno 2] No such file or directory
```
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par src/test/py/bazel:runfiles_test et reproduisez l’échec sous Windows avec `bazel test //src/test/py/bazel:runfiles_test`, avec le test activé. Suivez la façon dont le wrapping d’un py_binary localise son binary.zip généré ; le travail est terminé lorsque le test enveloppé s’exécute correctement sous Windows sans l’erreur de fichier manquant.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- build-system
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 38/100