commit e61f5dff7fa556e34282c20701a7a40d456d4b00
author Nico Weber <thakis@chromium.org> Thu Jun 07 15:26:59 2018
committer Nico Weber <thakis@chromium.org> Thu Jun 07 15:26:59 2018
tree ebfa783301677e5a7ea7f1bba796d21670380744
parent 99fa72cc64fc2bc7efea6f0887fa297c31e7efc6

Remove chromium_win_10_fast_ring_gtests.

The comment says it's supposed to be the same as chromium_win_clang_gtests
and interactive_ui_tests, but
https://chromium-review.googlesource.com/c/chromium/src/+/1076594 added
interactive_ui_tests to the clang list, and
https://chromium-review.googlesource.com/c/1090818/ removed chromium_win_clang_gtests
in favor of just chromium_win_gtests since the test lists have become equal.

This adds a bunch of tests to chromium_win_10_fast_ring_gtests that have been
added to chromium_win_clang_gtests and chromium_win_gtests after
chromium_win_10_fast_ring_gtests was forked. From the comment, it sounds like
adding these tests is what we should've done in the first place.

(I'm asking around if anyone looks at this bot at all since it's red and
it looks like it hasn't been touched in a while. Maybe I'll delete it in
a follow-up.)

Bug: 843511
Change-Id: I1fdb044c666941eb9beb8df0b50438e5a035f063
Reviewed-on: https://chromium-review.googlesource.com/1090819
Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565273}