| commit | b14f770657e825acdb7a77eef5042ea73061db86 | [log] [tgz] |
|---|---|---|
| author | Sebastien Marchand <sebmarchand@google.com> | Thu Mar 09 20:55:09 2023 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 09 20:55:09 2023 +0000 |
| tree | e075f8f40302b0b38951b29ab7638e90b48ee26d | |
| parent | 59a27878ca51200c661046ff7e32cfd079f83aa2 [diff] |
[fuchsia] Override the product-bundle path for LSC runs LSC runs should run against the product-bundle created by the LSC bot. I pulled the test values from this LSC run: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Fuchsia/65768/overview and I run the ffx product-bundle commands locally to make sure that the paths are correct. led runs (this should be a no-op as these runs shouldn't set the gclient variables used here): - Linux Fuchsia : https://ci.chromium.org/swarming/task/60d7e79df7835c10?server=chromium-swarm.appspot.com - Linux Fuchsia FEMU : https://ci.chromium.org/swarming/task/60d7e771cf0cda10?server=chromium-swarm.appspot.com - Linux Fuchsia arm64 FEMU: https://ci.chromium.org/swarming/task/60d7e7d560ad1210?server=chromium-swarm.appspot.com Change-Id: I89fd0d7d6a43057f57a0900c3a01815a1ef74ea1 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/40041 Commit-Queue: Sébastien Marchand <sebmarchand@google.com> Reviewed-by: Zach Anderson <zra@google.com>
This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Actual builds can be seen at ci.chromium.org.
Supported repositories roll their .ci.yaml into flutter/infra, which updates what properties builds have. For example, flutter config specifies various dependencies the different tests require, which are then used by the flutter_deps recipe_module No modifications to flutter/infra are required to work on the recipes.
Tricium configurations recipes repo.
Running python recipes.py test train will execute all of the tests in this repository
Required binary is not found on PATH: cipd when testing locallyYou need to ensure depot_tools is installed. See Depot Tools Installation Tutorial