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

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


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

chromium-rel-mac10

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@436862  42.6652  292.422  30  good
chromium@436892  45.6716  293.099  30  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 672426

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_desktop
Test Metric: v8-gc-latency-mark-compactor_max/v8-gc-latency-mark-compactor_max
Relative Change: 7.05%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2506
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993848760515232784


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

| 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!

Archiving issues older than 2 years with no owner or component.