[roll] Roll infra/recipes [swarming_retry] Write task outputs to files The new swarming CLI (guarded behind the "swarming.prpc.cli" Buildbucket experiment) includes the entire task stdio in responses rather than silently truncating it to 16MB. However, the task stdio can be quite large for some testing tasks, which causes OOMs when loading it into memory in the JSON response from `swarming collect`, which can contain multiple task results. If we use the new CLI's option to instead write the task stdio directly to disk we can avoid loading multiple tasks' stdio into memory at the same time, which seems to be sufficient to avoid OOMs. Original-Bug: 329690757 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1006733 Original-Revision: d673f40675e644ba6728bda48587d8791a02d961 GitOrigin-RevId: d0658ef73aefac6a5555acb4a6d27201091eafb3 Change-Id: Ia9a47dd4b1af87677a3f11a56ba56c09c103dea7
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.