[roll] Roll fuchsia [tefmocheck] Suspend test may cause an OOPS while passing.

The suspend test checks that device successfully reaches the S3 (Suspend
To Ram) power state and then attempts to resume. At this stage we do not
expect resume to succeed and in fact it is likely there will be multiple
OOPSes caused by leaking BTIs. This does not reflect a failure of the
test, but simply the expected state of resume currently.

Original-Bug: 117528
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/788273
Original-Revision: 2ca60316114043527964a62424180140d9101514
GitOrigin-RevId: 6210e588863241e66d28a4892aa0d4d428b3cc00
Change-Id: Ia331b72a847e0a5f66abb3d6717ca760d722b86f
1 file changed
tree: a700941f95b0a6a100c68ccb31e1296fc1b5c941
  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.