Remove ostentatious interleaving of action output and progress messages. I traced the use of FileOutErr to only be in SkyframeActionExecutor. The other event types generally wouldn't be expected to have stdout/stderr in any case. Detailed changes: * Change writeToStream to never show the progress bar, the one place it was asked to show the progress bar now does so explicitly. * Move the display of any stdout/stderr to inside the switch cases that can have stdout/stderr in the first place, specifically before we redraw the progress bar. * Don't flush the terminal before printing stdout/stderr, I don't see a reason to do that. * Assert that no other events have stdout/stderr in the first place. PiperOrigin-RevId: 343589378
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
