New issue
Advanced search Search tips

Issue 625432 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

25.1%-25.3% regression in smoothness.tough_webgl_cases at 403199:403607

Project Member Reported by qyears...@chromium.org, Jul 3 2016

Issue description

Likely related to  bug 623174 .
 

===== 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@403198  16.6982  0.0027256  18  good
chromium@403607  16.6969  0.0024605  18  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 625432

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_webgl_cases
Test Metric: frame_times/http___www.khronos.org_registry_webgl_sdk_demos_google_particles_index.html
Relative Change: 0.00%
Score: 0

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


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

| 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 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@403217  16.7127  0.0101696   18  good
chromium@403607  16.7132  0.00761074  18  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 625432

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.gpu_rasterization_and_decoding.image_decoding_cases
Test Metric: frame_times/frame_times
Relative Change: 0.01%
Score: 0

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


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

| 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)
Test result moved at the same time as ref build result.

Sign in to add a comment