| commit | 7f0928fd95e81bc93b544a8ea92dcbf232f691e9 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@google.com> | Wed Apr 14 23:04:09 2021 +0000 |
| committer | CQ Bot <commit-bot@chromium.org> | Wed Apr 14 23:04:09 2021 +0000 |
| tree | 3953df52a614afc6770a02a7e3267029ca14616c | |
| parent | b17c3313a1648cc455866504ce0488ca192de931 [diff] |
[testsharder] Remove knowledge of test schema Recipes no longer parse any fields of tests.json or of the "tests" shard field produced by testsharder, instead passing them through as opaque JSON values. Until recently, recipes still needed to know the schema of tests.json in order to filter out and build host test targets. But that logic now lives in fint instead, so recipes don't need to know how to read tests.json. The only field that's still referenced here is "name", which is just to preserve a semblance of accuracy - i.e. tests are dicts, not strings. Bug: 51896 Bug: 67861 Change-Id: Iefe39794c0c6a769617151ceef82c0ca206347ec Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/513932 Commit-Queue: Oliver Newman <olivernewman@google.com> Fuchsia-Auto-Submit: Oliver Newman <olivernewman@google.com> Reviewed-by: Ina Huh <ihuh@google.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
Thnn 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. }, ... }