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.

Sign up for GitHub

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

Jump to bottom

Documentation should state exit code 38 is BES related #13969

Closed
brentleyjones opened this issue Sep 10, 2021 · 2 comments
Closed

Documentation should state exit code 38 is BES related #13969

brentleyjones opened this issue Sep 10, 2021 · 2 comments
Labels
help wanted Someone outside the Bazel team could own this not stale Issues or PRs that are inactive but not considered stale P2 We'll consider working on this in future. (Assignee optional) team-Core Skyframe, bazel query, BEP, options parsing, bazelrc type: feature request

Comments

@brentleyjones
Copy link
Contributor

Description of the problem / feature request:

https://docs.bazel.build/versions/main/guide.html#what-exit-code-will-i-get states that exit code 38 is reserved for google use. We've only seen it for BES upload related errors. Can the documentation be updated to state that (maybe lumping it with exit code 45)?

Have you found anything relevant by searching the web?
@gregestren gregestren added team-Remote-Exec Issues and PRs for the Execution (Remote) team untriaged type: feature request labels Sep 13, 2021
@coeuvre coeuvre added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Apr 8, 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 13, 2023
@brentleyjones
Copy link
Contributor Author

Not stale

@brentleyjones brentleyjones added not stale Issues or PRs that are inactive but not considered stale and removed stale Issues or PRs that are stale (no activity for 30 days) labels Jun 15, 2023
@coeuvre coeuvre added the help wanted Someone outside the Bazel team could own this label Sep 7, 2023
@coeuvre coeuvre added team-Core Skyframe, bazel query, BEP, options parsing, bazelrc and removed team-Remote-Exec Issues and PRs for the Execution (Remote) team labels Oct 20, 2023
@brentleyjones brentleyjones mentioned this issue Jan 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Someone outside the Bazel team could own this not stale Issues or PRs that are inactive but not considered stale P2 We'll consider working on this in future. (Assignee optional) team-Core Skyframe, bazel query, BEP, options parsing, bazelrc type: feature request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document exit code 38 as a BES error bazelbuild/bazel
3 participants
@brentleyjones @gregestren @coeuvre