[roll] Roll fuchsia [memory-monitor] Logic for crash report filing config

Crash reports won't be filed if an empty config file is present in
memory_monitor's namespace. The end goal is to cut down on the
total number of crash report uploaded by limiting crash
reporting to specific builds.

Original-Bug: 65472

TESTED=`fx test //src/developer/memory/monitor/tests`
TESTED=With config `k pmm oom 1` @ 9ad22065c8bbc5e0
TESTED=Without config `k pmm oom` @ 09ac28313f8bb822

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/457030
Original-Revision: 855fa724c86c08cfbda1e532391bdd6c2487fbab
GitOrigin-RevId: 533be6c33c88b90d1214ea308156326f6c807d18
Change-Id: I038b71ff2c2dfbfe233c11d7e63e7a6a121dad37
1 file changed
tree: 8224fe8f9403527bb4e9d37be47d20d561d3f6f4
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. flower
  8. jiri.lock
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.