[benchmarking] Log command when |CHECK|ing command exit status

Log the attempted command again if we are about to fail a |CHECK| due to
a non-zero exit status.  While it's technically possible to find this
information from the "Running ..." line above, there can be an arbitrary
amount of test logging in between that and the failure, making it
difficult to find when reading buildbot logs.

Test: CQ
Change-Id: If612934a42bf371a14d2c8239ed78d6a6a145b8c
1 file changed
tree: 79f79585953d92d9a9a26976c6cde63fb3ea41f6
  1. boards/
  2. build/
  3. buildtools/
  4. bundles/
  5. docs/
  6. examples/
  7. garnet/
  8. peridot/
  9. products/
  10. scripts/
  11. sdk/
  12. src/
  13. third_party/
  14. tools/
  15. zircon/
  16. .clang-format
  17. .dir-locals.el
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. AUTHORS
  22. BUILD.gn
  23. CODE_OF_CONDUCT.md
  24. CONTRIBUTING.md
  25. LICENSE
  26. OWNERS
  27. PATENTS
  28. README.md
  29. rustfmt.toml
README.md

Fuchsia

Pink + Purple == Fuchsia (a new operating system)

What is Fuchsia?

Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.

Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See the documentation.