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

Issue 656732 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.4% regression in speedometer at 425593:425593

Project Member Reported by jasontiller@chromium.org, Oct 17 2016

Issue description

This may have recovered, but I don't see an obvious reason. Kicking off a bisect just in case.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=656732

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


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

win-zenbook
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 17 2016

Cc: nedngu...@google.com
Owner: nedngu...@google.com

=== Auto-CCing suspected CL author nednguyen@google.com ===

Hi nednguyen@google.com, 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 : [telemetry] Log all running processes when telemetry fails to create browser on Android
Author  : nednguyen
Commit description:
  
This is to investigate what prevents adb from running.

BUG= chromium:656224 

TBR=sullivan@chromium.org,

Review-Url: https://codereview.chromium.org/2422903002
Commit  : 8d9c6a30251158764be186298f76d82ae5816e5e
Date    : Sun Oct 16 17:44:06 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N   Good?
chromium@425592                      6062.5   43.1303  12  good
chromium@425592,catapult@8d9c6a3025  6312.99  298.931  5   bad    <--
chromium@425592,catapult@5e0af8f7dc  6146.37  105.007  12  bad
chromium@425593                      6195.9   159.969  12  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 656732

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer
Test Metric: Total/Total
Relative Change: 3.80%
Score: 95.0

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


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

| 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: -nedngu...@google.com
Owner: robert...@chromium.org
There is very very little chance that CL could have caused any regression.
Status: WontFix (was: Untriaged)
This is just a noisy benchmark.

Sign in to add a comment