[roll] Roll fuchsia [lacewing] Refactor functional test BUILD groups.

Create separate groups for SL4F vs non-SL4F tests to unblock creating infra builders that target products without SL4F servers.

* Also refactored how test authors interact with BUILD files, they should only need to update the BUILD file closest to their test now and have their changes bubbled up through top-level test groups.

Soft-transition plan:
1) Submit this CL to add new groups. (this CL)
2) Update builder configs to use new groups.
3) Remove unused groups

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/913810
Original-Revision: 433d4db571b63c311e540437ffe23a69ce3ffcfe
GitOrigin-RevId: 9e97efd9800e294e2480cddfd41f9693186c7a05
Change-Id: Ib6cff1aa967ef374c0fc6f0b2b6d60b6fa9ca5d5
1 file changed
tree: 989be602c154415767f47b9e55928cb2fb30857e
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
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.