commit 0d4d0331a15e11f7d6ca819ca28521f24ca4647f
author Nico Weber <thakis@chromium.org> Mon Jul 16 17:51:50 2018
committer Commit Bot <commit-bot@chromium.org> Mon Jul 16 17:51:50 2018
tree be21369f5f09a8a94ea48f4ba1e8272ca695b199
parent cae0b1367d3501aadbecca03c151fea49a6b6c18

Move unit_tests from chromium_gtests to chromium_gtests_for_devices_with_graphical_output.

chromium_gtests_for_devices_with_graphical_output means "not cast".
The cast build doesn't include anything at the //chrome level, and
unit_tests lives at the //chrome level.

Currently we have unit_tests in chromium_gtests which runs on all bots,
and then an exception to remove it again on the cast bots.

Instead, put it in chromium_gtests_for_devices_with_graphical_output so that
it only runs on non-cast bots in the first place.

(It also ends up removing unit_tests from linux-blink-heap-incremental-marking
and linux-blink-heap-verification on the fyi waterfall, since these bots run
chromium_gtests instead of chromium_linux_gtests -- that looks like a bot
config bug, but it's only FYI bots anyways.)

This removes the last "unclear why" comment from test_suite*.pyl!

Bug: 843511,817779,812533
Change-Id: I76e0a2b30e0ca87c02c73cb46d8135d9ab7030d8
Reviewed-on: https://chromium-review.googlesource.com/1138333
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575339}