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

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


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

linux-release

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970458743891322432

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/HTML5Rocks

Revision             Result                  N
chromium@493977      16.7586 +- 8.41497      14      good
chromium@494891      29.6433 +- 10.5302      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=HTML5Rocks loading.desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970458743891322432


For feedback, file a bug with component Speed>Bisection

kouhei: just like in  bug 757993 , HTML5Rocks site fails to produce values when bisecting. Anything we can do here?

sullivan: Would you help me on this? I tried to look in to the log for: https://chromeperf.appspot.com/buildbucket_job_status/8970458743891322432

but, I get the below message:
"This build is configured to send log data exclusively to LogDog. Please click the LogDog link on the build page to view this log stream."

I tried clicking on the LogDog link which takes me to 
https://luci-milo.appspot.com/buildbot/tryserver.chromium.perf/linux_perf_bisect/7561
But I still get the same message.

We're working on making it easier to find the logs in pinpoint, the new version of bisect. It's a little hard currently. Here are steps, and some links to logs:

1) Go to the buildbot status page: https://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/7561
2) Expand "Nested step(s) for: Bisecting revision (XX)" (any value of XX is fine. You can see a "Revision: chromium@494424" right above "Nested step(s)..." if you want to pick a particular commit position)
3) To see VALUES output by the test, click on "json.output" under "Bisecting revision.Reading chartjson results" (this step is repeated as many times as the test is repeated. You'll end up at a link like this: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Flinux_perf_bisect%2F7561%2F%2B%2Frecipes%2Fsteps%2FBisecting_revision__21_%2F0%2Fsteps%2FBisecting_revision.Reading_chartjson_results__442_%2F0%2Flogs%2Fjson.output%2F0
Reading the JSON, you can see something went wrong, because under "values", it's just null instead of a list of numbers.
4) To see LOGS, look for the step starting with "Bisecting revision.Performance Test " immediately above the values you looked at. Click on "stdout" link on that step. Example: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Flinux_perf_bisect%2F7561%2F%2B%2Frecipes%2Fsteps%2FBisecting_revision__21_%2F0%2Fsteps%2FBisecting_revision.Performance_Test_6_of_6__21_%2F0%2Fstdout
In the logs, you can also see links to traces ("View generated trace files online at https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/trace-file-id_1-2017-08-23_16-29-11-11962.html for story HTML5Rocks")

kouhei, did you still intend to look into this?

Looks like this page hasn't run since September. WontFix-ing, but kouhei, feel free to reopen if you're still investigating.