All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=797428

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=331c6b4a4c5e362ad0b4364e2b11fff7dfe1f022172a0e99a9df40d135d4c7c4


Bot(s) for this bug's original alert(s):

win
win-32

Assigning to the sheriff for the roll, ynovikov. Sorry for the late notice! Looks like the angle roll in r525897 regressed Windows binary size by ~200KiB. Is there anything that can be done? cc-ing Windows sizes owner grt as well.

This is expected from rolling Vulkan validation layers.
We could probably build Vulkan only for GPU bots for now, but it will be part of Chrome eventually.
Not sure if it's worth the effort to disable it temporarily.

This was previously closed as WontFix. Re-closing as such. The way rolling Vulkan works is by disabling it entirely, then re-enabling it afterwards, due to  issue 643346 .

 Issue 798347  has been merged into this issue.