| commit | db8f72508f53840def5ad410acd5a9bf511e763e | [log] [tgz] |
|---|---|---|
| author | Nicolas Sylvain <nsylvain@google.com> | Wed Jun 26 14:49:55 2019 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jun 26 14:49:55 2019 +0000 |
| tree | d995d33dc0e1897334db80c6a881bc08f8c6da8f | |
| parent | 18e89f2966cb3134ad9f8f7a0d82baa40e2b6cdd [diff] |
[cq] retry builders that timed out Currently only test failures are being retried in cq, and tests that hang are not considered as test failures. Given that we see a few test timeouts every day, and those CQ jobs require manual retries, I think we should consider those like normal test failures and retry automatically. Change-Id: Ib2b2fdccad5ec12e440a859257e702175c1805a3
This repository contains configuration files for infra services.
For the most part, the actual configs consumed by LUCI live under generated/. Those files are generated by executing the .star files at the root of the repository. Don't edit the generated files directly. Instead, edit the Starlark files and execute them to regenerate the generated/ files.
If you've checked out the infra repos using our Jiri manifest, then you should have a git hook that will automatically execute the starlark code and regenerate generated/*.cfg on git commit.
To manually execute the Starlark code, run:
../../fuchsia-infra/prebuilt/tools/lucicfg generate ./main.star
Or if you have lucicfg in your PATH, you can execute the .star files directly:
./main.star