Issue metadata
Sign in to add a comment
|
Android Nexus5X Perf failing *.tough_pinch_zoom_cases |
||||||||||||||||||||||
Issue descriptionRevision range first seen: 385938 : 385950 Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%282%29/builds/258/steps/smoothness.tough_pinch_zoom_cases/logs/stdio Looking in the revision range, it looks like https://chromium.googlesource.com/chromium/src/+/21d8ab14ef1f9ba1add62b264141bacc9fab0f90 may be responsible. boliu@, could your change have caused failures for the tough pinch zoom case tests? (Assigning to rschoen@, current perf sheriff.)
,
Apr 8 2016
Actually, *nothing* from libchrome.so got symbolized correctly. Might have to do with the .so being mapped directly to memory from the apk. Dunno..
,
Apr 28 2016
Any updates on this? This is still failing. Looking at Nexus 5x Perf (2) builder page (https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%282%29?numbuilds=200) this looks like it's been failing since around Mar 31? Trying a bisect: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/123
,
Apr 29 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : variations: Also enable the RenderingPipelineThrottling feature Author : skyostil Commit description: In addition to enabling the RenderingPipelineThrottling field trial, also enable the corresponding feature to actually test the feature on the waterfall. BUG= 487937 Review URL: https://codereview.chromium.org/1845223002 Cr-Commit-Position: refs/heads/master@{#384293} Commit : 904b8f7f89b62c48bdaf78553fc3b0830f3ac16c Date : Thu Mar 31 16:04:23 2016 ===== TESTED REVISIONS ===== Revision Exit Code Std Dev N Good? chromium@384203 0 N/A 10 good chromium@384277 0 N/A 10 good chromium@384287 0 N/A 10 good chromium@384292 0 N/A 10 good chromium@384293 1 N/A 10 bad <-- chromium@384294 1 N/A 10 bad chromium@384296 1 N/A 10 bad chromium@384314 1 N/A 10 bad chromium@384351 1 N/A 10 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 601765 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_pinch_zoom_cases Test Metric: mean_frame_time/mean_frame_time Relative Change: Zero to non-zero Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/123 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014123228825471424 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5820802788753408 | 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! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by boliu@chromium.org
, Apr 8 2016