"Build completed successfully" reported twice when using `bazel run` and second one isn't filtered with `--ui_event_filters=-INFO`
See original GitHub issueDescription of the bug:
When a bazel run
build completes successfully it reports the success twice in the terminal output:
INFO: Build completed successfully, 2 total actions
INFO: Build completed successfully, 2 total actions
When using --ui_event_filters=-INFO
, it still reports the extra line once:
INFO: Build completed successfully, 2 total actions
What’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
On any project, run bazel run //a:label
and note the duplicated Build completed successfully
output.
Which operating system are you running Bazel on?
macOS 12.4
What is the output of bazel info release
?
release-5.2.0
If bazel info release
returns development version
or (@non-git)
, tell us how you built Bazel.
No response
What’s the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD
?
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
"Build completed successfully" line printed twice by run ...
The underlying reason is that the UI event handler stores a string with a message to print if nothing else is happening, and...
Read more >What is causing duplicate builds of same target in Bazel?
First, one note is that the host configuration is being mostly deprecated, and "exec" is usually preferred. Some info about that is here: ......
Read more >Commands and Options | Bazel
Some commands, like build or test , can operate on a list of targets. They use a syntax ... which are built and...
Read more >Build programs with Bazel
To run Bazel, go to your base workspace directory or any of its subdirectories and ... INFO: Build completed successfully, 1 total action....
Read more >Command-Line Reference | Bazel
Individual writes are still reported in a single event, even if larger ... If all targets are up-to-date, the build completes successfully.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Since the original commit was rollbacked, I’ll remove the “potential release blocker” label.
@bazel-io flag