[roll] Roll fuchsia [power][broker] Use runner in integration tests

* Use more granular timing, rather than immediately returning from
  SetLevel, which allows us to verify the changes triggered by current
  level changes occur only after the return.
* Retain the previous level_control versions of the test and mark them
  with a TODO to be removed after level_control is removed. The changes
  to the tests can be seen by comparing Base to Patchset 7.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1225706
Original-Revision: 03f73420fdf4dc2391090daa5964cf4b75c25026
GitOrigin-RevId: c280b3ae2d70258e65cd92387c6a255b84a207e6
Change-Id: I936bb2b9baa6dca8901776d6de8992b7bff88630
1 file changed
tree: 847c14b1d41748d26448db2c601d81484574cf31
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 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.