[web tests] Separate expectations using more than one mutually exclusive specifier
This CL also adds the ability to remove configurations from expectations that do not have bugs. This CL also affects the behavior of the rebaseline and try-flag tools so that it will create expectations which do not have more than one mutually exclusive specifier. It also adds a new presubmit check which prevents users from creating expectations that contain more than one mutually exclusive specifier. We are doing this because the new test expectations format does not allow expectations to have more than one mutually exclusive specifier. Bug: 986447 Change-Id: Ic97c4f1bba1e57b71f4624ef88ad69b5c8122a9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970297 Commit-Queue: Rakib Hasan <rmhasan@google.com> Reviewed-by:Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#726015}
Showing
This diff is collapsed.
Please register or sign in to comment