All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=602766

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2LqW6gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2LqW6gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-JC-9QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-IiuvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguOaAvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguJmQuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguI-EpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2Ku__AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguO6xvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguJDA-gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguJCUlwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2LfisQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguMrorgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2JrdvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2PeMvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2JrJrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2KuGuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2PeMvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2LeEoAkM


Bot(s) for this bug's original alert(s):

chromium-rel-mac-hdd
chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11

Attempting another bisect: https://chromeperf.appspot.com/buildbucket_job_status/9014910614018581936

This is a pretty serious regression, but the tool I need to figure out where things went horribly wrong (i.e., the bisect tool) is simply not working.

prasadv: Any ideas?

There was an issue in the bisect parsing of build properties when checking build progress. crbug.com/605221.
Roberto fixed this one, I re-rekicked the job
https://chromeperf.appspot.com/buildbucket_job_status/9014556715681438688

The regression fully recovered.