The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/09213deb7b16aea386d27883a73ba4b1860d7e1c

commit 09213deb7b16aea386d27883a73ba4b1860d7e1c
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Mon Oct 02 23:54:58 2017

[Sheriff] Update expectations for fast/forms/suggested-value.html

webkit_layout_tests failing on Win7

https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7/builds/56163

TBR=mkwst@chromium.org

Bug: 770971
Notry: True
Change-Id: I35034ffbbd1a0d727920855544b8d8519895156d
Reviewed-on: https://chromium-review.googlesource.com/696131
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#505860}
[modify] https://crrev.com/09213deb7b16aea386d27883a73ba4b1860d7e1c/third_party/WebKit/LayoutTests/TestExpectations

> https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7/builds/56163

With this page, we can know the culprit CL.  We should have reverted the CL instead of marking the test in TestExpectations file.

The culprit CL was reverted for another reason. #505860 should be reverted too.

> With this page, we can know the culprit CL.  We should have reverted the CL instead of marking the test in TestExpectations file.

It's not always obvious which CL is responsible for the breakage out of 20 possible culprits, especially when a sheriff doesn't work in the area of the failing test.  Ideally, we try to revert the CL that caused the breakage, but the top priority is to keep the tree in a good state.

If the breaking CL has been removed, I'm happy to revert revision 505860.  For posterity, and my own information, which was the culprit CL of the 20?

#505743 touched the test.
I think The CL was relanded and the failure restarted.