[Telemetry] Should not "warn" when computing TBM

Warnings should be reserved for (non-fatal) things that did not happen
as expected. Computing TBM metrics on TBM benchmarks is expected, so
don't warn about it.

Keeps the stdout when running benchmarks locally a bit more clean
(while still keeping the info on logs).

Change-Id: I0193adbc2852ef7c9085cf8fd3d4ed75205865f3
Reviewed-on: https://chromium-review.googlesource.com/1112013
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Juan Antonio Navarro PĂ©rez <perezju@chromium.org>
1 file changed
tree: 7abb57ecc4f6b3d01d5da5bc2bf2c91682a0bee7
  1. bin/
  2. catapult_build/
  3. common/
  4. dashboard/
  5. dependency_manager/
  6. devil/
  7. docs/
  8. experimental/
  9. firefighter/
  10. hooks/
  11. infra/
  12. netlog_viewer/
  13. systrace/
  14. telemetry/
  15. third_party/
  16. trace_processor/
  17. tracing/
  18. web_page_replay_go/
  19. .eslintignore
  20. .eslintrc
  21. .gitignore
  22. .vpython
  23. AUTHORS
  24. codereview.settings
  25. CONTRIBUTING.md
  26. LICENSE
  27. navbar.md
  28. OWNERS
  29. PRESUBMIT.py
  30. pylintrc
  31. README.md
  32. WATCHLISTS
README.md

Catapult

Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:

These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.

Contributing

Please see our contributor's guide

Current build status