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

An --execution-log-level= flag that determines the level of execution logging #13269

Open
Buzz-Lightyear opened this issue Mar 26, 2021 · 5 comments
Labels
not stale Issues or PRs that are inactive but not considered stale P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Performance Issues for Performance teams type: feature request

Comments

@Buzz-Lightyear
Copy link

ATTENTION! Please read and follow:

  • if this is a question about how to build / test / query / deploy using Bazel, or a discussion starter, send it to bazel-discuss@googlegroups.com
  • if this is a bug or feature request, fill the form below as best as you can.

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 and runner 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.

Replace this line with your answer.

What operating system are you running Bazel on?

Mac

What's the output of bazel info release?

 smuthu  in  ~/Sandbox/learning-ios   on branch  master   > bazel info release
INFO: Using Bazel Remote listening on 127.0.0.1:64126
INFO: Running Bazel version 3.7.0
INFO: Invocation ID: f6042bf5-0c8b-471c-b186-734140b26e4b
release 3.7.0

If bazel info release returns "development version" or "(@non-git)", tell us how you built Bazel.

Replace this line with your answer.

What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?

https://github.com/bazelbuild/bazel.git
05c4aaa1cb6cb0943543aee6bb371124d5ca1179
05c4aaa1cb6cb0943543aee6bb371124d5ca1179

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

@Buzz-Lightyear Buzz-Lightyear changed the title An --execution-log-level= flag that determines the _level_ of execution logging An --execution-log-level= flag that determines the level of execution logging Mar 26, 2021
@aiuto aiuto added type: feature request team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website untriaged labels Mar 31, 2021
@philwo
Copy link
Member

philwo commented Jan 24, 2022

@meisterT Do you know if there is a way to get this information using currently available features?

@philwo philwo added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed untriaged labels Jan 24, 2022
@meisterT
Copy link
Member

I don't think so; moving it to our team anyway.

@meisterT meisterT added team-Remote-Exec Issues and PRs for the Execution (Remote) team team-Performance Issues for Performance teams and removed team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website team-Remote-Exec Issues and PRs for the Execution (Remote) team labels Jan 24, 2022
@altonchuzhan
Copy link

hi, are there any ways to get remote cache hit status of one specific target.

@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
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 Jun 27, 2023
@meisterT meisterT reopened this Jun 27, 2023
@meisterT meisterT 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 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not stale Issues or PRs that are inactive but not considered stale P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Performance Issues for Performance teams type: feature request
Projects
None yet
Development

No branches or pull requests

5 participants