Issue metadata
Sign in to add a comment
|
5.6%-90.8% regression in smoothness.tough_webgl_cases at 427351:427388 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8997739337017138448
,
Oct 26 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@427350 160.8 13.469 18 good chromium@427388 161.494 15.8885 18 bad Bisect job ran on: winx64_zen_perf_bisect Bug ID: 659622 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.tough_webgl_cases Test Metric: mean_frame_time/http___kenrussell.github.io_webgl-animometer_Animometer_tests_3d_webgl.html Relative Change: 6.29% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/567 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997739337017138448 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5231376326983680 | 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!
,
Oct 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8997722039980316304
,
Oct 26 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/569 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.
,
Feb 3 2017
These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982636249643998928
,
Apr 11 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: winx64_zen_perf_bisect Benchmark : smoothness.tough_webgl_cases Metric : mean_frame_time/http___webglsamples.org_aquarium_aquarium.html 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.aquarium.aquarium\.html' smoothness.tough_webgl_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982636249643998928 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5250119631372288 | 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 |
|||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Oct 26 2016