commit | d673f40675e644ba6728bda48587d8791a02d961 | [log] [tgz] |
---|---|---|
author | Oliver Newman <olivernewman@google.com> | Fri Mar 15 18:03:46 2024 +0000 |
committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 15 18:03:46 2024 +0000 |
tree | 0ad14c46850e4e23874114107ca3f72b4c390859 | |
parent | 741919024ab9c59544bb1a83fc7e66b7bafa6ecb [diff] |
[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. Bug: 329690757 Change-Id: I3bad5be91a6e9c9e33900450ccdaaf389aacbde2 Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1006733 Fuchsia-Auto-Submit: Oliver Newman <olivernewman@google.com> Reviewed-by: Ina Huh <ihuh@google.com> Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
This repository contains recipes for Fuchsia.
A recipe is a Python script that runs a series of commands, using the recipe engine framework from the LUCI project. We use recipes to automatically check out, build, and test Fuchsia in continuous integration jobs. The commands the recipes use are very similar to the ones you would use as a developer to check out, build, and test Fuchsia in your local environment.
See go/fuchsia-recipe-docs for complete documentation and a guide for getting started with writing recipes.
The recommended way to get the source code is with jiri. A recipe will not run without vpython
and cipd
, and using these recommended jiri manifests will ensure that you have these tools.
You can use the fuchsia infra Jiri manifest or the internal version (Googlers-only). Once that manifest is imported in your local jiri manifest, jiri update
should download vpython
and cipd
into <JIRI ROOT>/fuchsia-infra/prebuilt/tools/
. If you add that directory to your PATH, you should be good to go.
If you're just trying to make a single small change to in this repository and already have your local environment set up for recipe development (e.g. because you work with another recipes repository) you can simply clone this repository with git:
git clone https://fuchsia.googlesource.com/infra/recipes
Then it will be up to you to ensure that vpython
and cipd
are available in your PATH.
We format python code using Black, an open-source Python autoformatter. It should be in your PATH if you followed the instructions for setting up your environment.
After committing recipe changes, you can format the files in your commit by running black .
in your project root.
Many editors also have a setting to run Black automatically whenever you save a Python file (or on a keyboard shortcut). For VS Code, add the following to your workspace settings.json
to make your editor compatible with Black and turn on auto-formatting on save:
{ "python.formatting.provider": "black", "python.formatting.blackPath": "<absolute path to the black executable>", "[python]": { "editor.formatOnSave": true, "editor.rulers": [88], // Black enforces a line length of 88 characters. }, ... }