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

Issue 592008 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

64.6%-597.3% regression in blink_perf.svg at 378838:378885

Project Member Reported by lanwei@google.com, Mar 4 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 Value  Std. Dev.   Num Values  Good?
chromium@378837         98.118171   3.829238    41          good
chromium@378885         97.566244   3.853215    41          bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 592008

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests blink_perf.svg
Test Metric: FoodLeifLodahl/FoodLeifLodahl
Relative Change: 2.30%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/503
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9019106288540843040


| 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 label Cr-Tests-AutoBisect.  Thank you!
Cc: ashej...@chromium.org
Bisect re-kicked with wider revision range.

Details on the below link:

-------------------------
https://chromeperf.appspot.com/group_report?bug_id=592008

Thank you!
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Mar 11 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 Value  Std. Dev.   Num Values  Good?
chromium@378805         76.891778   3.501981    27          good
chromium@378930         77.774654   3.520915    26          bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 592008

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests blink_perf.svg
Test Metric: CrawFishGanson/CrawFishGanson
Relative Change: 4.46%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/516
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018513381200693808


| 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 label Cr-Tests-AutoBisect.  Thank you!
Status: WontFix (was: Assigned)
This has recovered.

Sign in to add a comment