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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=ee8f958cac82bd7458abbeb173462980f546dcd54a3889c69cfe379e6d1e144c


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

android-nexus5
android-nexus5X
android-one

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12825370440000

sullivan,simonhatch: seems pinpoint job is hung? Running for 17 hours and, if I'm reading the results right, the culprit appears to be pretty clearly pointed @ r538587.

Add MemoryAblation to field_trial_config by mariakhomenko@chromium.org

dtu, simonhatch, can one of you take a look per #3?

Yeah I think you're right, checked the commit positions on the 2 and that looks like the right culprit.

Don't think this is hung, it's currently waiting on 2 more changes since it seems to think there's more potential differences. The android-one devices look a bit overloaded though, so it might take a while to finish.

Still running after 30 hours... seems like it should report earlier when it has enough confidence prior to finishing everything?

Hmm kinda like if the regression is clearly the largest, report that right away?

Yeah

Cool, filed https://github.com/catapult-project/catapult/issues/4294 for the suggestion