New issue
Advanced search Search tips

Issue 648886 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 644865



Sign in to add a comment

65% regression in page_cycler_v2.intl_ar_fa_he at 418220:418250

Project Member Reported by toyoshim@chromium.org, Sep 21 2016

Issue description

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 21 2016

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2201
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.

Blockedon: 644865
FYI: The most recent bisect was kicked with 6 repeats just to see if bisection on PCv2 actually works now; we may need to kick another bisect with more repeats if that one doesn't repro.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Sep 22 2016


===== 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@418219  1734.95  255.158  18  good
chromium@418250  1720.48  352.547  18  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 648886

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_ar_fa_he
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.masrawy.com_
Relative Change: 5.50%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2203
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000894455308669776


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

| 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!
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Sep 22 2016

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2204
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.

Kicked with a wider range since it seems the regression might start before the range.
Project Member

Comment 12 by 42576172...@developer.gserviceaccount.com, Sep 26 2016


===== 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@418142  1776.41  320.807  18  good
chromium@418250  1815.26  289.742  18  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 648886

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_ar_fa_he
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.masrawy.com_
Relative Change: 0.97%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2206
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000477764178952288


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

| 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: WontFix (was: Assigned)
could be a noise

Sign in to add a comment