New issue
Advanced search Search tips

Issue 674931 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

42.1% regression in v8.browsing_desktop at 424083:437898

Project Member Reported by mlippautz@google.com, Dec 16 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=674931

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


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

chromium-rel-win7-x64-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 16 2016

Owner: mlippautz@chromium.org

=== PERF REGRESSION ===


=== Auto-CCing suspected CL author mlippautz@chromium.org ===

Hi mlippautz@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


===== 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@424082  8.56317  2.51315   6  good
chromium@430990  8.70217  2.92866   6  good
chromium@434444  2.7435   0.205634  6  good
chromium@436171  6.98867  1.33011   6  good
chromium@437035  2.59467  1.48909   6  good
chromium@437251  3.03733  1.514     6  good
chromium@437252  8.655    2.29995   6  bad    <--
chromium@437253  8.76367  3.92346   6  bad
chromium@437255  8.41633  1.71967   6  bad
chromium@437258  8.80067  1.11956   6  bad
chromium@437265  8.63283  2.84347   6  bad
chromium@437278  9.646    2.08743   6  bad
chromium@437305  8.42733  2.87228   6  bad
chromium@437359  8.99933  1.88913   6  bad
chromium@437467  9.15517  3.09323   6  bad
chromium@437898  11.373   2.47183   6  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 674931

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard v8.browsing_desktop
Test Metric: v8-gc-incremental-finalize_sum/browse_news/browse_news_flipboard
Relative Change: 32.81%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1554
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993107034328543232


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

| 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!
Cc: -mlippautz@chromium.org
Status: Fixed (was: Untriaged)
Flag relanded and regression recovered.

Sign in to add a comment