[roll] Roll fuchsia [Lacewing] Move calling FFX.setup and FFX.close

from
  mobly test class (setup_class and teardown_class)
to
  mobly controller (create and destroy)

As FFX (and Fuchsia-Controller) calls are being made in mobly_controller
get_info() which gets called in clean_up step of mobly test that starts
after teardown_class

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/865564
Original-Revision: 5b9afd2f17d45c7941501ffd108d8cb22ec39e91
GitOrigin-RevId: 5a9970eab579f6d2e312e612d3460c379a4190da
Change-Id: I048ca7258e8e1b3ac31b65bbe07a9fd766c5960c
1 file changed
tree: 293cf5c1493c4653094d41687e431356615fd10d
  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.