Issue metadata
Sign in to add a comment
|
163.2% regression in cc_perftests at 419532:419562 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 20 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000974621648961952
,
Sep 20 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1010 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.
,
Oct 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999609236876684208
,
Oct 6 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1077 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.
,
Oct 6 2016
perf sheriff fixit: unassigning bugs owned by perf sheriffs to clarify that the rotation is responsible for triage.
,
Oct 26 2016
,
Dec 17 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8993073889384820080
,
Dec 17 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range. Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@419531 N/A N/A 0 good chromium@419562 N/A N/A 0 bad Bisect job ran on: android_s5_perf_bisect Bug ID: 648700 Test Command: src/build/android/test_runner.py gtest --release -s cc_perftests --verbose Test Metric: layer_tree_host_frame_time/10_10_threaded_impl_side_leaf_invalidates Relative Change: 0.00% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1168 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993073889384820080 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5841971329892352 | 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!
,
Dec 21 2016
These will all be invalid as they are specific to Samsung S5s, which we do not trust to give us a signal and have subsequently removed from the waterfalls. If you think this regression is real, please re-open.
,
Dec 21 2016
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982584718974047008 |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by jasontiller@chromium.org
, Sep 20 2016