New issue
Advanced search Search tips

Issue 601897 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 601898
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

60.4% regression in blink_perf.bindings at 385750:385788

Project Member Reported by rsch...@chromium.org, Apr 8 2016

Issue description

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

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


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

android-nexus5X
Cc: erikc...@chromium.org
Owner: erikc...@chromium.org

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

Hi erikchen@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : ipc: Rename TakeFileHandleForProcess->TakePlatformFileForTransit.
Author  : erikchen
Commit description:
  
This CL has no intended behavior change. This CL also removes the now
unnecessary parameter |process|.

BUG= 493414 

Review URL: https://codereview.chromium.org/1862333002

Cr-Commit-Position: refs/heads/master@{#385781}
Commit  : 41e608362245c754380232a2effdce714987f530
Date    : Thu Apr 07 16:37:14 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@385749         70.685023   2.620503    12          good
chromium@385769         71.695649   1.670273    8           good
chromium@385779         70.235455   2.259445    18          good
chromium@385780         70.531148   2.910684    18          good
chromium@385781         73.388938   2.832039    18          bad         <-
chromium@385782         74.02387    1.571005    12          bad
chromium@385784         74.612737   1.5924      5           bad
chromium@385788         73.554216   2.909107    12          bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 601897

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests blink_perf.bindings
Test Metric: insert-before/insert-before
Relative Change: 2.97%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/64
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015920051831447600


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

| 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!
Components:
This seems impossible, but the bisect looks pretty straightforward. Trying again to confirm.
Mergedinto: 601898
Status: Duplicate (was: Assigned)
Whoops, duplicate bug.

Sign in to add a comment