commit 3e8653c84d3a3ae72376ad9dbdfb97af50fec705
author Oliver Newman <olivernewman@google.com> Tue Dec 22 00:17:09 2020 +0000
committer CQ Bot <commit-bot@chromium.org> Tue Dec 22 00:17:09 2020 +0000
tree 5ab6fd0b0e92f8d604842ffa95f7fbc31c03d740
parent dfeaf8e23067305d3b531359a932689cb7479fe6

[testsharder] Lower max runs for multiplied tests

Multiplying a test many times can cause issues processing and uploading
the resulting shard's logs and test results, because they might be
massive. This is especially bad for automatically multiplied tests,
where the fact that the builder is running any multiplied shards is
generally (as it should be) completely opaque to the CL owner. For
example: https://ci.chromium.org/b/8860625698851501456

To make such processing failures less common, reduce the maximum number
of test runs that testsharder will calculate from 2000 to 1000. This
shouldn't have much user-facing impact, as the limit doesn't apply to
user-specificied run counts. For example, "MULTIPLY: foo_test: 5000"
will still run foo_test 5000 times, but "MULTIPLY: foo_test" will never
run foo_test more than 1000 times now.

Change-Id: I214826a2bbc0808395fe87eedac147ec04458ba5
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/464614
Fuchsia-Auto-Submit: Oliver Newman <olivernewman@google.com>
Reviewed-by: Ina Huh <ihuh@google.com>
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>