First failure: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win10/builds/15124 https://codereview.chromium.org/2362963003 seems to have introduced it.
And I don't like to revert it since it contains expectations changes for other parts. I'm not particularly familiar with layout tests and the process around that.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f8307f1db4915635d9bf4c7df5e48347adeaccea commit f8307f1db4915635d9bf4c7df5e48347adeaccea Author: tkent <tkent@chromium.org> Date: Fri Sep 23 13:04:19 2016 More rebaseline of form-validation-reportValidity.html. BUG= 649633 TBR=grunell@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2353393005 Cr-Commit-Position: refs/heads/master@{#420610} [add] https://crrev.com/f8307f1db4915635d9bf4c7df5e48347adeaccea/third_party/WebKit/LayoutTests/platform/linux/imported/wpt/html/semantics/forms/constraints/form-validation-reportValidity-expected.txt [add] https://crrev.com/f8307f1db4915635d9bf4c7df5e48347adeaccea/third_party/WebKit/LayoutTests/platform/win/imported/wpt/html/semantics/forms/constraints/form-validation-reportValidity-expected.txt
Comment 1 by grunell@chromium.org
, Sep 23 2016