Windows, test wrapper: changes to logging

In this commit:

- Drop support for `--no_echo`. As far as I can
  tell neither is this feature used nor can it be
  triggered from Bazel.

- Update the logging functions to use WriteFile
  instead of printf. This ensures the output is
  immediately flushed, instead of being printed
  after the subprocess' output (as was the case).

- Drop `stdio.h` usage since we don't need printf
  anymore, and use `cstdio` and std::ios_base
  instead.

See https://github.com/bazelbuild/bazel/issues/5508

Closes #6728.

PiperOrigin-RevId: 222382823
3 files changed
tree: 8ccf115ec688c654590fc7f772c8d3f4f5c321c0
  1. .bazelci/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .gitattributes
  9. .gitignore
  10. AUTHORS
  11. BUILD
  12. CHANGELOG.md
  13. CODEOWNERS
  14. combine_distfiles.py
  15. combine_distfiles_to_tar.sh
  16. compile.sh
  17. CONTRIBUTING.md
  18. CONTRIBUTORS
  19. distdir.bzl
  20. ISSUE_TEMPLATE.md
  21. LICENSE
  22. README.md
  23. WORKSPACE
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel only rebuilds 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.

Getting Started

Documentation

Contributing to Bazel

See CONTRIBUTING.md

Build status

Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.