[roll] Roll infra/recipes [fuchsia] Disable check for duplicated perf metrics for multiplied tests

If a perf test gets multiplied in a try build (using the "Multiply:"
feature) such that it gets run multiple times across different shards
(which will happen if it has "isolated = true" set in GN), that will
cause the checks done by the "summary of perf test results" recipe
step (done by perfcompare.py) to fail.

Address that problem by turning off those checks if any tests are
multiplied.

This fix is a bit of a hack because the tests that cause the problem
aren't actually run in shards with the name prefix "multiply:" --
shards for tests with "isolated = true" aren't given that prefix when
they're multiplied.  This might be a bug in testsharder.

In future it might be better to make perfcompare.py's checks more
sophisticated, so it knows which results come from multiplied tests
and can take the "Multiply:" feature into account.

I have not attempted to add a test case for this because that is
relatively difficult to do with the recipes framework and because this
fix is somewhat hacky.

Original-Bug: 477975823
Test: none
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1488140
Original-Revision: a7857a1d1a7f843ff0eeb1ba132c6eb09792fd99
GitOrigin-RevId: f671e5e8f83741283ad71b82fdeeeec7f0835a10
Change-Id: I2eb2101e4ee3bc5ad24e91f143eb6d16b4b45a5b
1 file changed
tree: f4c4d19c0048f68ed3ac7272935d66bf581dac6d
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  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 in one of the communication channels documented at get involved.

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.