[fuchsia] Fix the log collection step

There's no need to specify the emulator log path as we're using an
isolated config, we can simply read the log files directly. This does that and remove the explicit call to `ffx log dump`. It often happens that we need the logs because the ffx connection has dropped, reading the log files directly will help debug these issues.

led run:  https://ci.chromium.org/swarming/task/60f732f302e8bc10?server=chromium-swarm.appspot.com

Change-Id: Ibc93b86515839fdcde942bf973401741108d9e8d
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/40361
Reviewed-by: Zach Anderson <zra@google.com>
Commit-Queue: Sébastien Marchand <sebmarchand@google.com>
11 files changed
tree: dd0cc091293d52062ec911116d3e8658299f8300
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. .gitignore
  5. .style.yapf
  6. AUTHORS
  7. LICENSE
  8. OWNERS
  9. README.md
  10. recipes.py
README.md

Flutter LUCI Recipes

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.

Configuration

Tricium configurations recipes repo.

Testing locally

Running python recipes.py test train will execute all of the tests in this repository

Troubleshooting

Required binary is not found on PATH: cipd when testing locally

You need to ensure depot_tools is installed. See Depot Tools Installation Tutorial