Fix browser detection with custom local build dirs

The browser finder eagerly scans all out/* dirs for known chrome
types. If there are any non-standard names it hard crashes which
blocks us from running tests.

Change-Id: I927b4d643a69555b5c8b83932c460c68f4dadacf
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/7557071
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Reviewed-by: Wenbin Zhang <wenbinzhang@google.com>
2 files changed
tree: 97e643bca2593df9038e8ef8e45488065ad932db
  1. bin/
  2. catapult_build/
  3. common/
  4. dashboard/
  5. dependency_manager/
  6. devil/
  7. docs/
  8. experimental/
  9. hooks/
  10. infra/
  11. netlog_viewer/
  12. perf_issue_service/
  13. skia_bridge/
  14. systrace/
  15. telemetry/
  16. third_party/
  17. trace_processor/
  18. tracing/
  19. .eslintignore
  20. .eslintrc
  21. .gcloudignore
  22. .gitignore
  23. .gitmodules
  24. .style.yapf
  25. .vpython3
  26. .yapfignore
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. CONTRIBUTING.md
  31. DEPS
  32. DIR_METADATA
  33. generate_telemetry_build.py
  34. LICENSE
  35. navbar.md
  36. OWNERS
  37. PRESUBMIT.py
  38. pylintrc
  39. README.md
  40. 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