-
Notifications
You must be signed in to change notification settings - Fork 4k
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
An --execution-log-level=
flag that determines the level of execution logging
#13269
Comments
--execution-log-level=
flag that determines the _level_ of execution logging--execution-log-level=
flag that determines the level of execution logging
@meisterT Do you know if there is a way to get this information using currently available features? |
I don't think so; moving it to our team anyway. |
hi, are there any ways to get remote cache hit status of one specific target. |
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 ( |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team ( |
Description of the problem / feature request:
I'd like an
--execution-log-level=
flag that determines the level of execution logging we'd like. Currently there's a single--execution_log_binary_file
which is pretty large and contains more info than we might need at times.Feature requests: what underlying problem are you trying to solve with this feature?
Given the option to set the execution log level, customers can prioritize how much information they need in the execution logs. The smaller execution log that I have in mind contains just the
mnemonic
andrunner
fields (We want to get granular remote cache hit stats)Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
Mac
What's the output of
bazel info release
?If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
?Have you found anything relevant by searching the web?
There are couple of open issues about remote cache hit metrics but none about changing the size of execution logs
Any other information, logs, or outputs that you want to share?
Not in particular
The text was updated successfully, but these errors were encountered: