Fix and re-enable v8.infinite_scroll benchmarks on Windows |
|||||
Issue descriptionThe v8.infinite_scroll benchmarks are causing issues on Windows (both ignition and non-ignition). It appears that the Facebook page is specifically problematic. Example first failing build: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf%20%281%29/builds/4081 I'm going to disable these two benchmarks on Windows. To debug this issue, trying to run the Facebook page on a Windows box (by passing --story-filter=facebook when running run_benchmark) would be a good place to start.
,
Aug 22 2016
Looks like the whole benchmark needs some love. Do we still need them though, I think we already have upgraded ones?
,
Aug 22 2016
The logs also get spammed with messages containtin "Error: double-handled event 50808 50808 [object Object]"
,
Aug 30 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9002891952338391280
,
Aug 30 2016
It is clearly a regression between https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf%20%281%29/builds/4080 and https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf%20%281%29/builds/4081 Started returned code bisect: https://chromeperf.appspot.com/buildbucket_job_status/9002891952338391280
,
Aug 31 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [Editing][CSS] Drag from a -webkit-user-select:none element should not start selection Author : yoichio Commit description: This CL is updated of reverted one: https://codereview.chromium.org/2001993002 This CL considers the reverted shadow boundary issue. BUG= 481985 Review-Url: https://codereview.chromium.org/2021793002 Cr-Commit-Position: refs/heads/master@{#412457} Commit : 08acdf950e1776571def8e6f16c288769e7e9e27 Date : Wed Aug 17 06:16:52 2016 ===== TESTED REVISIONS ===== Revision Exit Code Std Dev N Good? chromium@412450 0 N/A 20 good chromium@412455 0 N/A 20 good chromium@412456 0 N/A 20 good chromium@412457 1 N/A 20 bad <-- chromium@412458 1 N/A 20 bad chromium@412460 1 N/A 20 bad Bisect job ran on: winx64_10_perf_bisect Bug ID: 638724 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll_tbmv2 Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:peak_size_avg/discourse Relative Change: Zero to non-zero Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/701 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002891952338391280 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5299322382450688 | 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!
,
Aug 31 2016
I cannot reproduce the failure locally. Maybe it was fixed in the meantime. I'll try to re-enable the benchmark.
,
Oct 12 2016
This was fixed long time ago. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Aug 18 2016