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

Issue 661483 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

26.1% regression in tracing.tracing_with_debug_overhead at 427812:427881

Project Member Reported by primiano@chromium.org, Nov 2 2016

Issue description

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

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


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

chromium-rel-mac-hdd
Cc: rnep...@chromium.org
Owner: rnep...@chromium.org

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

Hi rnephew@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 : [Common] Move WaitFor from telemetry to common/py_utils
Author  : rnephew
Commit description:
  
BUG=catapult:#2955

Review-Url: https://codereview.chromium.org/2451553006
Commit  : 6bdd081cfd114ef91e5c5518afd6bbd13dff9a6f
Date    : Wed Oct 26 19:30:33 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N  Good?
chromium@427811                      15292.0  763.3    5  good
chromium@427846                      16764.6  1687.37  5  good
chromium@427864                      16513.6  1143.14  5  good
chromium@427873                      16039.9  1405.79  8  good
chromium@427875                      15984.4  1550.7   5  good
chromium@427876                      16290.6  945.685  5  good
chromium@427876,catapult@631691de62  16556.8  785.815  5  good
chromium@427876,catapult@6bdd081cfd  21150.8  1870.98  5  bad    <--
chromium@427877                      20274.3  1128.23  8  bad
chromium@427881                      21589.0  1042.02  5  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 661483

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests tracing.tracing_with_debug_overhead
Test Metric: Max number of events per second_sum/Max number of events per second_sum
Relative Change: 41.18%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/868
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997113017448670304


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

| 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!
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
This bug is over 10 months old; I think we missed the window to fix.

Sign in to add a comment