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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghongqAoM


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

chromium-rel-mac-retina

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev     N   Good?
chromium@407922  0.101871  0.0012282   18  good
chromium@407961  0.102643  0.00148241  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 632179

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: queueing_durations/queueing_durations
Relative Change: 1.16%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1455
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005943784086824640


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6068841927409664

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Perf sheriff ping: reminder to follow up on possible performance issues

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev      N   Good?
chromium@407922  0.102584  0.00190115   17  good
chromium@407961  0.102848  0.000966334  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 632179

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: queueing_durations/queueing_durations
Relative Change: 0.47%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1625
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002882261829972640


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5014501424889856

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

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

I kicked off a bisect on a more specific page, but it's looking like this does not reproduce.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev     N   Good?
chromium@407922  0.121468  0.00544151  18  good
chromium@407961  0.118418  0.00674909  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 632179

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: queueing_durations/touch_handler_scrolling.html?janky_handler
Relative Change: 1.83%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1680
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000695243871579008


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5776754512232448

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Fixit ping: I kicked a slightly wider bisect.

Assigning to reporter aiolos@ for further triage.

Adding test owners skyostil@ and brianderson@. Folks, any idea about next steps here?

Hmm, the regression looks pretty clear so I'm not sure why the bisect is having difficulties. Nothing really jumps out of the patch list either...

Actually looking at a larger window of values looks like the metric has practically recovered.