[chromeperf] Pinpoint cancel all swarming builds if a try job fails

In a try job, if one branch has the build failed, the Pinpoint job will
fail. However, the other build of the other branch will continue and
thus become a waste of builder resource.

This CL tries to cancel the builds when a try job fails.

To limit the scope, it only handles:
 - when the job type is try job.
 - only cancel the builds, not the test runs.
 - only when the Pinpoint job fails, not when it is canceled.

Change-Id: If465a3cf365c73bd36d0b8dbee976e9a45c9f5c4
Bug: 445817923
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/7282107
Commit-Queue: Wenbin Zhang <wenbinzhang@google.com>
Reviewed-by: John Chen <johnchen@chromium.org>
6 files changed
tree: fb1865b7102b9602f42599165e0d38b8b1305d52
  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. web_page_replay_go/
  20. .eslintignore
  21. .eslintrc
  22. .gcloudignore
  23. .gitignore
  24. .style.yapf
  25. .vpython3
  26. .yapfignore
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. CONTRIBUTING.md
  31. DIR_METADATA
  32. generate_telemetry_build.py
  33. LICENSE
  34. navbar.md
  35. OWNERS
  36. PRESUBMIT.py
  37. pylintrc
  38. README.md
  39. 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