Issue metadata
Sign in to add a comment
|
wasm/WasmZenGarden in wasm failing on multiple builders |
||||||||||||||||||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of ashleymarie@google.com wasm/WasmZenGarden in wasm failing on multiple builders Builders failed on: - Mac 10.12 Perf: https://ci.chromium.org/buildbot/chromium.perf/Mac%2010.12%20Perf - Mac Air 10.11 Perf: https://ci.chromium.org/buildbot/chromium.perf/Mac%20Air%2010.11%20Perf - Win 10 High-DPI Perf: https://ci.chromium.org/buildbot/chromium.perf/Win%2010%20High-DPI%20Perf - Win 10 Perf: https://ci.chromium.org/buildbot/chromium.perf/Win%2010%20Perf - Win 7 Nvidia GPU Perf: https://ci.chromium.org/buildbot/chromium.perf/Win%207%20Nvidia%20GPU%20Perf - mac-10_12_laptop_low_end-perf: https://ci.chromium.org/buildbot/chromium.perf/mac-10_12_laptop_low_end-perf
,
May 14 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14b23130240000
,
May 14 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a185745cb40a356a37535438f9d19e37136b225e commit a185745cb40a356a37535438f9d19e37136b225e Author: Ashley Enstad <ashleymarie@chromium.org> Date: Mon May 14 19:02:09 2018 Disabling warmzengarden Bug: 842729 Change-Id: I66e634c272f445ea2eb482722251a68fca0579bb TBR=eyaich@ Change-Id: I66e634c272f445ea2eb482722251a68fca0579bb Reviewed-on: https://chromium-review.googlesource.com/1057832 Commit-Queue: Ashley Enstad <ashleymarie@chromium.org> Reviewed-by: Emily Hanley <eyaich@chromium.org> Reviewed-by: Ashley Enstad <ashleymarie@chromium.org> Cr-Commit-Position: refs/heads/master@{#558400} [modify] https://crrev.com/a185745cb40a356a37535438f9d19e37136b225e/tools/perf/expectations.config
,
May 14 2018
,
May 18 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/14b23130240000 __init__() got an unexpected keyword argument 'scope'
,
May 23 2018
https://chromium.googlesource.com/v8/v8/+/a83277498ca7f2719138226fbbe8660b5f818571 is Wasm related in the range. @Ashleymarie: What's up with Pinpoint? @Wasm folks: Clemens (the reviewer) is OOO, can somebody of you please take a look?
,
May 23 2018
,
May 24 2018
@dtu: thoughts about pinpoint failure?
,
May 25 2018
,
May 25 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12cc8d32240000
,
May 26 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12cc8d32240000 [turbofan][x64] Reduce compare-zero followed by flags-setting binop by kanghua.yu@intel.com https://chromium.googlesource.com/v8/v8/+/423343635042c2d9b05a850ebc1d2fc3fc9cc4f5 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
May 28 2018
Ah, we already fixed the issue introduced by "[turbofan][x64] Reduce compare-zero followed by flags-setting binop".
,
May 29 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d1ad79bef331ee38990a85f4a0109704dd785557 commit d1ad79bef331ee38990a85f4a0109704dd785557 Author: Andreas Haas <ahaas@chromium.org> Date: Tue May 29 14:23:25 2018 Enable wasmzengarden The problem why the benchmark got disabled has been fixed, see https://crbug.com/842501 . We should re-enable the tests again. R=eyaich@chromium.org Bug: chromium:842729 Change-Id: Ieb5acf000a5feddba2098b384c0be3607b433c31 Reviewed-on: https://chromium-review.googlesource.com/1075519 Reviewed-by: Emily Hanley <eyaich@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#562414} [modify] https://crrev.com/d1ad79bef331ee38990a85f4a0109704dd785557/tools/perf/expectations.config |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ashleymarie@chromium.org
, May 14 2018