The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/8ce59fa0d561f71818a08c62d2158b15c616f1c5

commit 8ce59fa0d561f71818a08c62d2158b15c616f1c5
Author: Chan <chanli@chromium.org>
Date: Tue Aug 21 20:42:50 2018

[Findit] Also record aborted try job pipelines if they are for resumed try job after heuristic pipeline aborts.

Normally Findit uses one root analyze_xxx_failure_pipeline to run heuristic analysis then try job. But if heuristic analysis failed and aborts the pipeline, we can try to resume try job if required data have been collected. And in that case, start_xxx_try_job_pipeline becomes the root pipeline.

In this case, we need to collect the number of aborted pipelines separately.

Bug: 867173
Change-Id: Id9e6f6b263704630a056306687e04426796f2c73
Reviewed-on: https://chromium-review.googlesource.com/1149195
Commit-Queue: Chan Li <chanli@chromium.org>
Reviewed-by: Roberto Carrillo <robertocn@chromium.org>

[modify] https://crrev.com/8ce59fa0d561f71818a08c62d2158b15c616f1c5/appengine/findit/pipelines/compile_failure/test/analyze_compile_failure_pipeline_test.py
[modify] https://crrev.com/8ce59fa0d561f71818a08c62d2158b15c616f1c5/appengine/findit/services/build_failure_analysis.py
[modify] https://crrev.com/8ce59fa0d561f71818a08c62d2158b15c616f1c5/appengine/findit/pipelines/test_failure/start_test_try_job_pipeline.py
[modify] https://crrev.com/8ce59fa0d561f71818a08c62d2158b15c616f1c5/appengine/findit/pipelines/compile_failure/test/start_compile_try_job_pipeline_test.py
[modify] https://crrev.com/8ce59fa0d561f71818a08c62d2158b15c616f1c5/appengine/findit/pipelines/test_failure/test/start_test_try_job_pipeline_test.py
[modify] https://crrev.com/8ce59fa0d561f71818a08c62d2158b15c616f1c5/appengine/findit/pipelines/compile_failure/start_compile_try_job_pipeline.py
[modify] https://crrev.com/8ce59fa0d561f71818a08c62d2158b15c616f1c5/appengine/findit/pipelines/test_failure/test/analyze_test_failure_pipeline_test.py