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

Issue 663952 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 663911



Sign in to add a comment

12.9% regression in smoothness.tough_webgl_cases at 430723:430809

Project Member Reported by rsch...@chromium.org, Nov 10 2016

Issue description

See the link to graphs below.
 
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 10 2016

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/588
Failure reason: the build has failed.

Blockedon: 663911
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 11 2016


===== BISECT JOB RESULTS =====
Status: failed


=== 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.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@430722  16.7222  0.321472  27  good
chromium@430809  16.7818  0.616818  27  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 663952

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...webglsamples.org.blob.blob.html smoothness.tough_webgl_cases
Test Metric: mean_frame_time/http___webglsamples.org_blob_blob.html
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/598
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996258215523320384


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

| 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!
Re-kicked bisect due to blocker being fixed.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Nov 15 2016


===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@430722  16.6874  0.155771  27  good
chromium@430809  16.6955  0.215459  27  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 663952

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...webglsamples.org.blob.blob.html smoothness.tough_webgl_cases
Test Metric: mean_frame_time/http___webglsamples.org_blob_blob.html
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/602
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995897235632256608


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

| 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: Untriaged)
These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.
Project Member

Comment 12 by 42576172...@developer.gserviceaccount.com, Apr 10 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : smoothness.tough_webgl_cases
  Metric       : mean_frame_time/http___webglsamples.org_blob_blob.html

Revision             Result                   N
chromium@430722      16.7795 +- 0.590579      21      good
chromium@430809      16.7373 +- 0.194834      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...webglsamples.org.blob.blob.html smoothness.tough_webgl_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982667403853258880

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4988910638202880


| 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 Speed>Bisection.  Thank you!

Sign in to add a comment