[roll] Roll infra/recipes [fuchsia] Upload skipped shards to ResultDB

Fixes a regression introduced in
commit 0133e681fb915dcd67604587d3be19bf052bfc8e. That commit moved
ResultDB uploads from the fuchsia.py recipe into the testing recipe
module's launch/collect loop, but that code only runs for shards that
actually have corresponding Swarming tasks run, not for shards that are
skipped.

So add logic back to fuchsia.py to explicitly upload results for skipped
shards.

Original-Fixed: 422754692
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1293664
Original-Revision: 648c4b58264974a08638353d823c85c7da4d1a1f
GitOrigin-RevId: 87e44d1ceb4de56054c052fe3339c79108f6fff9
Change-Id: I40b27972bac065e533628ba79b14b6268b1cbad0
1 file changed
tree: 57e18341dae42ca4a0d305a415915d51e884ab95
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. 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.