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

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


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

android-nexus5
android-nexus5X
android-webview-nexus6

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12e72f6d840000

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

Trying another bisect.

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14b629ee440000

+dtu: looks like the test isn't producing values and there's not much we can do to bisect?

Yes, but that leads to the question: why did it produce values on the perf waterfall but not bisect?

I don't know! Simon, who do you think would lead an investigation of why a test produced values on perf dashboard but not pinpoint?

Think it should start with us making sure we're parsing the data correctly. There seems to be valid histogram output, Dave got time to look at this? Otherwise punt it to me and I'll dig through.

Looks like the story being passed in from dashboard is "nytimes", but the story in the histogram output is "http://nytimes.com/". So it can't find the story.

We've probably seen a bunch of these.

I think these were all migrated in  crbug.com/818035 

Might be able to bisect this if we specify the old name, hopefully it doesn't overlap the range where the names were changed.

Filed a tracking bug here: https://github.com/catapult-project/catapult/issues/4346

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

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

(Watch out for the webview bots, they're super overloaded)

Ah true, can you kill the job I started in #15 then?

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/158daeb9440000

Looks like it's not sufficient to just change the "story" in the bisect form. The "trace" comes from the code.

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11924945440000

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

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

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12dddceb440000

Dave, can you look at the pinpoint error?

Looks like the story changed name in dashboard, so the bisection was run on the wrong story name.
(https://github.com/catapult-project/catapult/issues/4346)

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/16f592ab440000

Thanks, Dave!

WontFix-ing since this is a pretty small bump, and larger bumps later in the graph were able to be bisected, so not super worried about the story name change from #26.