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

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


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

win

Assigning to angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com because this is the only CL in range:
Roll src/third_party/angle/ 40dba6908..ed8b49195 (4 commits)

https://chromium.googlesource.com/angle/angle.git/+log/40dba69082bd..ed8b49195844

$ git log 40dba6908..ed8b49195 --date=short --no-merges --format='%ad %ae %s'
2018-03-07 jmadill Vulkan: Fix missing depth/stencil access flags.
2018-03-02 jmadill Add RenderTargetCache helper.
2018-03-07 ynovikov Revert "Add NPOT validation to copyTextureCHROMIUM"
2018-03-06 tobine Roll (2/2) to latest LVL as of 3/6/18

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=ynovikov@chromium.org

Change-Id: Ia569df5da9d8c64bf0ae27133237b8586e9e789e
Reviewed-on: https://chromium-review.googlesource.com/954051
Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#541721}

ynovikov: the angle roll above caused a 200KiB increase in Windows binary size, as sheriff for the roll, can you take a look?

This is not actually a regression, we roll Vulkan Validation Layers by disabling, rolling and reenabling. Thus, the size is the same as prior to disabling.