New issue
Advanced search Search tips

Issue 648616 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 644865



Sign in to add a comment

39.3%-521.9% regression in page_cycler_v2.tough_layout_cases at 419322:419370

Project Member Reported by jasontiller@chromium.org, Sep 20 2016

Issue description

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

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


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

chromium-rel-mac-hdd
chromium-rel-mac-retina
Project Member

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/805
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
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Sep 23 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@419321  211.398  57.325   18  good
chromium@419368  191.175  25.9753  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 648616

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.tough_layout_cases
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___indoritel.com
Relative Change: 2.81%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1677
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000778493743324144


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

| 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 8 by 42576172...@developer.gserviceaccount.com, Sep 27 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@419321  197.255  48.297   18  good
chromium@419368  190.387  20.7681  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 648616

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.tough_layout_cases
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___indoritel.com
Relative Change: 5.80%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1691
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000430192460687872


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

| 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!
Owner: ----
perf sheriff fixit: unassigning bugs owned by perf sheriffs to clarify that the rotation is responsible for triage.
Status: Untriaged (was: Assigned)
Status: Archived (was: Untriaged)
Archiving as bisection is difficult and there's been no movement.
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Apr 11 2017

Bisect failed: None
Failure reason: incorrect bisect configuation.
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.

Sign in to add a comment