[roll] Roll fuchsia [vmstress] Cap max threads in MultiVmoTestInstance Prevent the max number of threads that are spawned by MultiVmoTestInstance from exceeding 300 to avoid overloading the system. 300 should be insteresting enough for parallel VMO accesses. Restore max test instances to 8 (from 4). The most number of threads is spawned by MultiVmoTestInstance of which there is a single instance. The other test instance types spawn only six threads per instance. So capping MultiVmoTestInstance should be sufficient to control the overall thread count. Original-Bug: 109364 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/727225 Original-Revision: 3b1a8252a3a5c17fad6e8867954297a1c9167403 GitOrigin-RevId: 1043f4ab262376297a1813f7b52edcb9f450046f Change-Id: I07b2a00f2fd57809493c6322d44321b73ddc3c91
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.