GitLab

Note that this change also reshards the Win 7 Builders, which
may cause false positive regressions. In the event of
perf regressions, this CL should not be reverted, since it
is not causing the regression; it is just moving the test
to run on a different device (of the same model and OS).

Also, move to only use 4 shards instead of 5. We are seeing
that these bots die sometimes (examples: crbug.com/1038720,
crbug.com/1038719), so it is better to keep one device in
reserve to help out if another one dies.

See
https://chromium-review.googlesource.com/c/chromium/src/+/1983326
for background.

This moves all the gtest perf tests on Win 7 Perf and Win 7
Nvidia GPU Perf into the performance_test_suite and onto the
shard maps. This allows us to run them in parallel with the Telemetry
benchmarks and account for their runtime within our system.

Bug: 921353
Change-Id: I284924447435325da2263131e0b7df6411b04e4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985134
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Auto-Submit: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728068}