[roll] Roll fuchsia [tefmo] Detect when devices are incorrectly unlocked

We should never have unlocked devices running tasks in infra.  In the
event that happens anyway, we might observe failures when end-to-end
tests rely on accessing secrets that are only available when locked.

Flag these so that Infra can go re-lock them.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/727188
Original-Revision: 2e578fda99d0e828cbc9acc04401049838a3971d
GitOrigin-RevId: b81e05e935e2afe2964ec47c2ca74e8b0077655c
Change-Id: I61535badba67d0bfc33a64f9a0f992a5ba4d083c
1 file changed
tree: be4193a0198da7f6c9773c43ecc962903a475e34
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.