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
Pants Pex releases broke w/ venv mode #11954
Labels
Comments
The issue is a sys.path entry of pants/src/python/pants/option/global_options.py Lines 1364 to 1374 in d401cc5
Changing the relpath line to |
More generally, the relpath should only be attempted for globs that are absolute paths in the first place. |
Eric-Arellano
added a commit
to Eric-Arellano/pants
that referenced
this issue
Apr 21, 2021
pantsbuild#11955) Works around pantsbuild#11954. `--unzip` should give still good enough of performance. [ci skip-rust]
Eric-Arellano
added a commit
that referenced
this issue
Apr 21, 2021
More progress on #11952. There is nothing left in Bash except for the processing of options, which then pipes to Python; and setting the Python interpreter to run the Python script. `release.sh` will be removed in a followup. This adds lightweight validation to our PEX build process, which would have caught #11954. Certainly, we should be building the PEX via `./pants package` instead of directly via PEX. But this is an incremental improvement from before. [ci skip-rust]
stuhood
added a commit
to stuhood/pants
that referenced
this issue
Mar 17, 2022
…b calculation. (pantsbuild#14819) Fixes pantsbuild#11954. [ci skip-build-wheels] # Rust tests and lints will be skipped. Delete if not intended. [ci skip-rust]
Eric-Arellano
added a commit
that referenced
this issue
Mar 17, 2022
Makes sure that #11954 won't happen again.
stuhood
added a commit
to stuhood/pants
that referenced
this issue
Mar 30, 2022
…b calculation. (pantsbuild#14819) Fixes pantsbuild#11954. [ci skip-build-wheels] # Rust tests and lints will be skipped. Delete if not intended. [ci skip-rust]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
They originally worked when added for 2.4.0.dev0 in #11591, but broke somewhere in between there and 2.4.0.0rc1 (no PEX releases between then, which was unintentional).
I time boxed myself investigating this, so am not sure why this is happening yet. However, using
--unzip
mode fixes the issue.--
Beyond the underlying Pex issue this might reveal, it shows the need for our release process to add a smoke test to building PEXes, something as simple as running
--version
.The text was updated successfully, but these errors were encountered: