New issue
Advanced search Search tips

Issue 645580 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

88.3% regression in page_cycler_v2.top_10_mobile at 416105:416147

Project Member Reported by rsch...@chromium.org, Sep 9 2016

Issue description

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

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


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

chromium-rel-mac11
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/883
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.

Owner: dtu@chromium.org
What do we do with these, when the test name has changed?
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/883
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.

Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Sep 10 2016

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

ping dtu, what do we do with these where the test name changes?
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Sep 17 2016

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

===== 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@416104  86.8482  13.5934  18  good
chromium@416147  112.245  29.2749  18  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 645580

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.top_10_mobile
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/https___m.facebook.com_rihanna
Relative Change: 20.38%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/939
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001970922998177264


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

| 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!
Perf sheriff ping
Blockedon: -644865
One bot, no ref build results, bisect didn't reproduce. Trying one more bisect; if it fails then this should be closed.
Project Member

Comment 18 by 42576172...@developer.gserviceaccount.com, Oct 20 2016

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

Status: WontFix (was: Assigned)
Bisect hasn't been able to reproduce. Closing per recommendation. 

Sign in to add a comment