[roll] Roll fuchsia [tests][oom] Fix test race where we wait for a wrong message

This change fixes a bug in the oom_test that was introduced with the
kernel.oom.trigger-on-alloc-failure feature.  Depending on the exact
nature of the OOM event we may or may not observe the memory pressure
state change message.

Test: Ran host_x64/oom_tests 10 times.
Original-Fixed: 94019
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/647801
Original-Revision: bcfeda7737f738960b2cbb14691c1ab089d2d78c
GitOrigin-RevId: 770a552781fe611b84fdf4695c008e0d6e5bf313
Change-Id: Ie6f9c464fb4ccffa15daf032cbcea865b816a690
1 file changed
tree: af10ceb5debb92816d537263a8ba473e9764fc14
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.