Run all unit tests on trybots to test changes better.
alex-paladin and link-paladin are the only two commit queues that run
all unit tests (even the unit tests of packages that weren't changed
in the CLs being tested). We do this so as to distribute the load over
the paladin builders (mario-paladin, x86-generic-paladin, and
amd64-generic-paladin run VMTests, so they're the long pole; meanwhile
alex-paladin and link-paladin have extra time to spare so we use them
to run extra unit tests)
When testing https://gerrit.chromium.org/gerrit/#/c/44968/, Chris
Masone ran a trybot run on stumpy-paladin, expecting that it would
adequately test his change. When he put his change through commit
queue, he was surprised to find out that it failed on alex and lumpy.
To help prevent this problem from happening in future, I'm going to
recommend we just always run all unit tests on the trybots, so as to
make it easier for developers who don't know these internal details
about which bots run full unit tests.
BUG=chromium-os:39775
TEST=Run trybot runs and verify they run all unit tests.
Change-Id: I25d024803887ef59a4ab686ff5419df4d12f5279
Reviewed-on: https://gerrit.chromium.org/gerrit/45030
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
1 file changed
