[roll] Roll fuchsia [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.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/464614
Original-Revision: 3e8653c84d3a3ae72376ad9dbdfb97af50fec705
GitOrigin-RevId: d83dcd2489a368060a1921aee658b9e5d181f3f0
Change-Id: Ic480a49d526d7a25909ffae6ac363667e9a33022
1 file changed
tree: acb5ba00587bc49c93375802d68d47cea4095531
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. flower
  8. jiri.lock
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.