New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 669559 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

25.9% regression in v8.infinite_scroll_tbmv2 at 434626:434641

Project Member Reported by benhenry@chromium.org, Nov 29 2016

Issue description

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

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


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

chromium-rel-win10
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 29 2016

Mergedinto: 669144
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : Revert of Reland "[wrapper-tracing] Enable flag per default" (patchset #1 id:20001 of https://codereview.chromium.org/2503043002/ )
Author  : mlippautz
Commit description:
  
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

Review-Url: https://codereview.chromium.org/2528393002
Cr-Commit-Position: refs/heads/master@{#434640}
Commit  : 2b5aa49038a8dd31697e3b9d636a26750a4ecdaa
Date    : Mon Nov 28 12:23:35 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@434625  0.654672  0.680245  15  good
chromium@434633  0.633136  0.748704  20  good
chromium@434637  0.637161  0.686166  20  good
chromium@434639  0.628922  0.582446  15  good
chromium@434640  0.831196  0.888672  25  bad    <--
chromium@434641  0.837522  0.720195  20  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 669559

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/788
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994639212887321680


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

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

Sign in to add a comment