Skip to content
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

execv error executing PEX in custom rule #14921

Closed
nickbreen opened this issue Mar 1, 2022 · 3 comments
Closed

execv error executing PEX in custom rule #14921

nickbreen opened this issue Mar 1, 2022 · 3 comments
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Python Native rules for Python type: support / not a bug (process)

Comments

@nickbreen
Copy link

Description of the problem / feature request:

Attempting to write a rule to use pex to build PEX's.

Getting a strange error from ctx.actions.run that does not manifest with a genrule or direct invocation outside of bazel.

Feature requests: what underlying problem are you trying to solve with this feature?

Define a simple pex_binary rule.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Minimal reproduction: https://github.com/nickbreen/bazel_pex

What operating system are you running Bazel on?

Fedora 34, Python 3.6 and 3.9

What's the output of bazel info release?

release 4.2.0

Have you found anything relevant by searching the web?

I've found a number of repos and issues on github for bazel and rules_python, etc; all of which appear to be inconclusive or appear ancient/abandoned:

Any other information, logs, or outputs that you want to share?

Please see https://github.com/nickbreen/bazel_pex

@aiuto aiuto added untriaged team-Rules-Python Native rules for Python labels Mar 2, 2022
@comius
Copy link
Contributor

comius commented Mar 10, 2022

Quick look, this looks like an error thrown by an action during its execution (not something thrown by Bazel).

@comius comius added P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) type: support / not a bug (process) and removed untriaged labels Mar 10, 2022
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Jun 14, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Python Native rules for Python type: support / not a bug (process)
Projects
None yet
Development

No branches or pull requests

3 participants