Issue metadata
Sign in to add a comment
|
cc_perftests failure on chromium.perf/Linux Perf (3) at 419369 - 419388 |
||||||||||||||||||||
Issue descriptionRevision range first seen: 419369 - 419388 Link to failing step log: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Linux%20Perf%20%283%29/builds/17738/steps/cc_perftests/logs/stdio If the test is disabled, please downgrade to Pri-2. Going to start a return code bisect on the range.
,
Sep 20 2016
Snoozing this for 4h in SOM (sheriff-o-matic).
,
Sep 20 2016
===== BISECT JOB RESULTS ===== Status: completed ===== TESTED REVISIONS ===== Revision Exit Code Std Dev N Good? chromium@419369 0 N/A 1 good chromium@419388 0 N/A 1 bad Bisect job ran on: linux_perf_bisect Bug ID: 648735 Test Command: ./src/out/Release/cc_perftests --test-launcher-print-test-stdio=always --verbose Test Metric: Compress256x256BlackAndWhiteGradientImage/ETC1 High Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6717 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000967616206099248 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5296995500032000 | 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!
,
Jan 28 2017
Marking this as WontFix (no movement in 3+ months) |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 20 2016