Bazel client: debug info for corrupt installation

The Bazel client checks the installation files
every time it starts. Bazel checks that it can
read the installation files and that their mtimes
are in the future.

The "bazel-tests" project on Bazel CI recently
produced flaky-looking failures. The error
messages talk about a missing installation file.

This change makes Bazel print more debugging info
when the aformentioned check fails. I hope the
information will help catching this bug.

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

Change-Id: Ic51384b5840262484515fa320f162a79cfd0e012
PiperOrigin-RevId: 166696141
1 file changed
tree: 48f35170608d17a6bf1867176b96395a4cac45d2
  1. examples/
  2. scripts/
  3. site/
  4. src/
  5. third_party/
  6. tools/
  7. .gitattributes
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CHANGELOG.md
  12. combine_distfiles.py
  13. combine_distfiles_to_tar.sh
  14. compile.sh
  15. CONTRIBUTING.md
  16. CONTRIBUTORS
  17. ISSUE_TEMPLATE.md
  18. LICENSE
  19. README.md
  20. 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 system. 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.