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

Issue 663117 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1%-16% regression in page_cycler_v2.intl_hi_ru at 429270:429349

Project Member Reported by briander...@chromium.org, Nov 7 2016

Issue description

See the link to graphs below.
 

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@429304  81.2407  3.84769  18  good
chromium@429305  80.1884  1.64802  18  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 663117

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_ko_th_vi
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___us.24h.com.vn_
Relative Change: 1.12%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1225
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996610072662334144


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

| 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!
Mergedinto: 661927
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : Add crash keys to TaskQueueManager::ProcessTaskFromWorkQueue
Author  : alexclarke
Commit description:
  
We suspect a bad task closure is getting posted and would like to
add crash keys to aid diagnosis.

BUG=660427

Review-Url: https://codereview.chromium.org/2464853002
Cr-Commit-Position: refs/heads/master@{#429285}
Commit  : c08c078b27b353f4ab8de7deccfb862270b1ff2a
Date    : Wed Nov 02 15:49:06 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@429248  69.5076  1.08375   5  good
chromium@429268  69.492   1.14301   5  good
chromium@429278  68.738   1.18946   5  good
chromium@429283  69.4602  1.58451   5  good
chromium@429284  69.8954  1.26073   5  good
chromium@429285  80.73    0.973392  5  bad    <--
chromium@429286  80.4798  2.50065   5  bad
chromium@429288  78.943   1.2015    5  bad
chromium@429328  78.9962  0.598551  5  bad
chromium@429407  79.875   1.53467   5  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 663117

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...us.24h.com.vn. page_cycler_v2.intl_ko_th_vi
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___us.24h.com.vn_
Relative Change: 14.92%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1227
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996523359591416496


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

| 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