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

Issue 669562 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

64.3% regression in memory.long_running_idle_gmail_background_tbmv2 at 434640:434666

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=669562

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


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

win-zenbook
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@434639  0.533662  0.278434    8  good
chromium@434640  0.721387  0.0775733   5  bad    <--
chromium@434641  0.708066  0.0870863   8  bad
chromium@434643  0.715701  0.114554    8  bad
chromium@434646  0.711308  0.0380157   5  bad
chromium@434653  0.713212  0.0618247   5  bad
chromium@434666  0.699974  0.00694626  5  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 669562

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/612
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994638855065931968


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

| 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