wasm/WasmStylizedRenderer and 1 other(s) in wasm failing on multiple builders |
||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org wasm/WasmStylizedRenderer and 1 other(s) 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 - Mac Pro 10.11 Perf: https://ci.chromium.org/buildbot/chromium.perf/Mac%20Pro%2010.11%20Perf - Win 10 High-DPI Perf: https://ci.chromium.org/buildbot/chromium.perf/Win%2010%20High-DPI%20Perf - Win 7 Intel GPU Perf: https://ci.chromium.org/buildbot/chromium.perf/Win%207%20Intel%20GPU%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 Looks like this is failing 100% of the time. Last successful run was 556060, first failing run was 556181. Going to disable and kick off a bisect.
,
May 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b8b2dcd2f8336e8f7a36f7581f0a3135c7d5386f commit b8b2dcd2f8336e8f7a36f7581f0a3135c7d5386f Author: Charlie Andrews <charliea@chromium.org> Date: Tue May 08 19:26:23 2018 Disable failing wasm stories NOTRY=true TBR=nednguyen@chromium.org CC=bradnelson@chromium.org Bug: 840935 Change-Id: I99ec329b99822a800d70da48dcea4a085fe71e56 Reviewed-on: https://chromium-review.googlesource.com/1050577 Reviewed-by: Charlie Andrews <charliea@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#556924} [modify] https://crrev.com/b8b2dcd2f8336e8f7a36f7581f0a3135c7d5386f/tools/perf/expectations.config
,
May 9 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12a4114fc40000 Reduce maximal code range size to 128M on Linux, Windows, and OSX for x64 and ia32. by hpayer@chromium.org https://chromium.googlesource.com/v8/v8/+/6b1457cfd6baa332ffa968b74fff705bac72e762 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
May 9 2018
,
May 9 2018
This should have been fixed with https://crrev.com/c/1049648.
,
May 14 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1d2ff61680be7427b20e484b2364279bbaa91088 commit 1d2ff61680be7427b20e484b2364279bbaa91088 Author: Charlie Andrews <charliea@chromium.org> Date: Mon May 14 14:39:11 2018 Revert "Disable failing wasm stories" This reverts commit b8b2dcd2f8336e8f7a36f7581f0a3135c7d5386f. Reason for revert: Problem has since been fixed. Original change's description: > Disable failing wasm stories > > NOTRY=true > TBR=nednguyen@chromium.org > CC=bradnelson@chromium.org > > Bug: 840935 > Change-Id: I99ec329b99822a800d70da48dcea4a085fe71e56 > Reviewed-on: https://chromium-review.googlesource.com/1050577 > Reviewed-by: Charlie Andrews <charliea@chromium.org> > Commit-Queue: Charlie Andrews <charliea@chromium.org> > Cr-Commit-Position: refs/heads/master@{#556924} TBR=nednguyen@google.com,charliea@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. NOTRY=true TBR=nednguyen@chromium.org Bug: 840935 Change-Id: If27b317e19ae8bfa876b16338102a181868c69f4 Reviewed-on: https://chromium-review.googlesource.com/1057365 Commit-Queue: Charlie Andrews <charliea@chromium.org> Reviewed-by: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#558297} [modify] https://crrev.com/1d2ff61680be7427b20e484b2364279bbaa91088/tools/perf/expectations.config
,
May 24 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 8 2018