Issue metadata
Sign in to add a comment
|
No data received for v8.infinite_scroll-ignition_tbmv2 from chromium-rel-win7-dual since 455470 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 27 2017
cc: ulan@ There is no entry for this ignition variant at go/chrome-benchmarks, but probably ulan@ can take a look?
,
Mar 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983984697801960464
,
Mar 27 2017
I think turbofan and ignition variants of this benchmark were disabled
,
Mar 27 2017
Thanks. So I could close this as WontFix. If you have any concern, please reopen this.
,
Mar 27 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: win_perf_bisect Benchmark : v8.infinite_scroll-ignition_tbmv2 Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_max/twitter Revision Exit Code N chromium@455470 0 +- N/A 20 good chromium@455600 0 +- N/A 20 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=twitter v8.infinite_scroll-ignition_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983984697801960464 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6407829440692224 | 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 toyoshim@chromium.org
, Mar 27 2017