https://findit-for-me.appspot.com/waterfall/check-flake?key=ag9zfmZpbmRpdC1mb3ItbWVyvAELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKFAWNocm9taXVtLm1hYy9NYWMxMC45IFRlc3RzIChkYmcpLzM3NTY3L2Jyb3dzZXJfdGVzdHMvVjI5eWEyVnlSR1YyVkc5dmJITlRZVzVwZEhsVVpYTjBMbEJoZFhObFNXNVRhR0Z5WldSWGIzSnJaWEpKYm1sMGFXRnNhWHBoZEdsdmJnPT0MCxITTWFzdGVyRmxha2VBbmFseXNpcxgBDA In this analysis, the previous build on buildbot had crashed, swallowing most of the blamelist. Thus findit's flake analyzer thought there was only 1 revision in the blamelist and was thus the culprit that introduced flakiness. Instead, pull the blame list directly from git for better reliability
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/9d065655ce158f368b4e1b63660536b39528e8cc commit 9d065655ce158f368b4e1b63660536b39528e8cc Author: Jeffrey Li <lijeffrey@chromium.org> Date: Fri Mar 10 22:10:30 2017 [Findit] Flake Analyzer - Get blame list from git BUG= 699676 Change-Id: I0fa8883345158683d6ed7a37b242e56d6f87c811 Reviewed-on: https://chromium-review.googlesource.com/452941 Commit-Queue: Jeffrey Li <lijeffrey@chromium.org> Reviewed-by: Chan Li <chanli@chromium.org> [modify] https://crrev.com/9d065655ce158f368b4e1b63660536b39528e8cc/appengine/findit/waterfall/test/process_flake_swarming_task_result_pipeline_test.py [modify] https://crrev.com/9d065655ce158f368b4e1b63660536b39528e8cc/appengine/findit/waterfall/process_flake_swarming_task_result_pipeline.py
Comment 1 by lijeffrey@chromium.org
, Mar 8 2017