New issue
Advanced search Search tips

Issue 661543 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

90.6% regression in page_cycler_v2.intl_ar_fa_he at 428985:429021

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

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


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

android-nexus6

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@428984  557.705  52.7102  5  good
chromium@429003  1041.2   176.338  5  bad
chromium@429021  827.289  112.307  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 661543

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_ar_fa_he
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___ynet.co.il_
Relative Change: 48.34%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2721
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997106591714932736


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

| 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!
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2725
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

First bisect failed due to device issues, second failed due to  bug 662472 
Blockedon: 662472

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


===== SUSPECTED CL(s) =====
Subject : Roll src/third_party/catapult/ 189969c9c..0d3575d73 (1 commit).
Author  : catapult-deps-roller
Commit description:
  
https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/189969c9c124..0d3575d73a47

$ git log 189969c9c..0d3575d73 --date=short --no-merges --format='%ad %ae %s'
2016-11-01 ksakamoto [loading metric] filter out events during cache warming

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2466903002
Cr-Commit-Position: refs/heads/master@{#428993}
Commit  : 3ce6f32d4fe45f351530fc4aef06d751e51d83cb
Date    : Tue Nov 01 14:05:35 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N   Good?
chromium@428987                      479.251  48.8048  8   good
chromium@428991                      526.077  115.595  8   good
chromium@428992                      717.58   127.934  27  good
chromium@428992,catapult@0d3575d73a  798.28   106.925  27  good
chromium@428993                      711.256  105.633  27  bad    <--
chromium@428994                      732.232  87.7217  8   bad
chromium@429001                      713.558  132.754  8   bad
chromium@429015                      776.679  101.456  5   bad
chromium@429043                      709.479  96.5582  5   bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 661543

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...ynet.co.il. page_cycler_v2.intl_ar_fa_he
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___ynet.co.il_
Relative Change: 50.95%
Score: 0.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2236
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996638938729448592


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

| 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!
Blockedon: -662472
Status: WontFix (was: Untriaged)
These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.
Labels: Performance-Loading

Sign in to add a comment