Reduce CLI output during fetch invocations #2048
Open
+15
−24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cjreynol
added
kokoro:force-run
GoogleCuttlefishTesterBot
removed
kokoro:run
Push the logging about cache hits to verbose. The long cache paths for multiple files were significantly increasing the output for fetches. The output still ends up in `fetch.log` by default.
cjreynol
force-pushed
the
reduce_fetch_cli_output
branch
from
07cba45 to
49fd045
Compare
cjreynol
added
kokoro:force-run
GoogleCuttlefishTesterBot
removed
kokoro:run
Databean
approved these changes
Jan 22, 2026
Comment on lines
+142
to
+143
| VLOG(1) << "Created hard link from \"" << target << "\" to \"" << hardlink | ||
| << "\""; |
Member
There was a problem hiding this comment.
Can the logs here be at VLOG(0) level so they at least show up in the fetch.log file? At least I think that's what the cutoff is.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Push the logging about cache hits to verbose-level logging. The long cache paths for multiple files were significantly increasing the output for fetches. The output still ends up in
fetch.logby default.