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

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


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

android-nexus6

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

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


=== Bisection aborted ===
The bisect was aborted because Infra Failure: Step('Working on revision chromium@437229,v8@93b87c89f2.install ChromePublic.apk') returned 2
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@437229  81.7515  178.08   6  good
chromium@437230  387.556  119.892  6  bad
chromium@437231  360.37   48.3727  6  bad
chromium@437232  362.489  30.7667  6  bad
chromium@437234  360.915  102.023  6  bad
chromium@437238  354.977  50.5072  6  bad
chromium@437247  354.439  42.1869  6  bad
chromium@437264  358.458  35.4101  6  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 673442

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.browsing_mobile
Test Metric: v8-gc-latency-mark-compactor_max/browse_news/browse_news_nytimes
Relative Change: 338.47%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2825
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993452497317112992


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

| 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/8992733428594516704

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


===== SUSPECTED CL(s) =====
Subject : Revert of "[wrapper-tracing] Enable flag per default" (patchset #3 id:140001 of https://codereview.chromium.org/2540743003/ )
Author  : mlippautz
Commit description:
  
Reason for revert:
Revert for upcomming dev release.

Original issue's description:
> Reland of land "[wrapper-tracing] Enable flag per default" (patchset #2 id:150001 of https://codereview.chromium.org/2528393002/ )
>
> Reason for revert:
> Dev release happened. Enabling again.
>
> Original issue's description:
> > Revert of Reland "[wrapper-tracing] Enable flag per default" (patchset #1 id:20001 of https://codereview.chromium.org/2503043002/ )
> >
> > Reason for revert:
> > Reverting because of upcomming Dev release. Will re-enable tomorrow after the release is done.
> >
> > Original issue's description:
> > > Reland "[wrapper-tracing] Enable flag per default"
> > >
> > > BUG= chromium:468240 
> > >
> > > Committed: https://crrev.com/e23de6962be8b4967127ae95040f32bbb533b4d1
> > > Cr-Commit-Position: refs/heads/master@{#433823}
> >
> > TBR=hlopko@chromium.org,haraken@chromium.org,hpayer@chromium.org,jochen@chromium.org
> > # Not skipping CQ checks because original CL landed more than 1 days ago.
> > BUG= chromium:468240 , chromium:668060, chromium:668059
> >
> > Committed: https://crrev.com/2b5aa49038a8dd31697e3b9d636a26750a4ecdaa
> > Cr-Commit-Position: refs/heads/master@{#434640}
>
> TBR=hlopko@chromium.org,haraken@chromium.org,hpayer@chromium.org,jochen@chromium.org
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG= chromium:468240 , chromium:668060, chromium:668059
>
> Committed: https://crrev.com/6dade445294d2a029c8c9407497ea7b883afe7ad
> Committed: https://crrev.com/d5f90d2760d39d11495039928fd5d9d777da7329
> Cr-Original-Commit-Position: refs/heads/master@{#435105}
> Cr-Commit-Position: refs/heads/master@{#436554}

TBR=hlopko@chromium.org,haraken@chromium.org,hpayer@chromium.org,jochen@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= chromium:468240 , chromium:668060, chromium:668059
NOTRY=true

Review-Url: https://codereview.chromium.org/2562713003
Cr-Commit-Position: refs/heads/master@{#437252}
Commit  : 192be7f967328bde3f05894c5c75d08213b7d6ad
Date    : Thu Dec 08 16:05:03 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@437241  1.56955  0.238999  9  good
chromium@437251  1.56706  0.086596  9  good
chromium@437252  1.85252  0.226351  6  bad    <--
chromium@437253  1.81406  0.236652  6  bad
chromium@437254  1.76298  0.300615  6  bad
chromium@437256  1.77436  0.267537  6  bad
chromium@437261  1.75661  0.28406   6  bad
chromium@437280  1.78405  0.36439   9  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 673442

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.long_running_idle_gmail_tbmv2
Test Metric: v8-gc-total_avg/v8-gc-total_avg
Relative Change: 13.67%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2845
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8992733428594516704


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

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