Remove pending stanza from post-run action

Also execute to actually apply the changes, I forgot this in
my previous change.

The post_actions are only triggered when the LUCI recipe terminates, so
it will never match the pending stanza. Unfortunately this means a rerun
on the same patchset will not reset the Frontend-Verified vote when the
new run starts.

Change-Id: Id080f6c773dbe31f63e634bcc7bdcd418864179e
2 files changed
tree: cd0aa7047bfecd89594eca42db37028bf6cede51
  1. generated/
  2. infra/
  3. recipes/
  4. repos/
  5. .gitignore

LUCI Configuration

This repo holds all the configuration for LUCI, the CI system Gerrit uses. You can find recent verification runs and logs at


  • Recipe: a python script to verify a change, and a test for that verification
  • Builder: a recipe configured to run on a specific machine type
  • CQ Group: a watcher that triggers on new votes/patchsets on the specified repo+refs
  • CQ Tryjob Verifier: combines a CQ group with a builder to run a recipe when a new vote or patchset comes in


  • / overall starlark configuration for the entire host. It is also executable to generate the config data
  • /repos/*.star: repo-specific starlark configuration for builders, CQ groups, CQ tryjob verifiers, etc
  • /recipes/recipes/*.py: recipes for testing a change based on the repo
  • /recipes/ executes recipe tests and compares/generates expected JSON goldens. 100% coverage is expected.
  • /recipes/recipe_modules/: dependencies shared by modules
  • /recipes/*.expected/*.json: expected commands executed by the recipe
  • /infra/config/recipes.cfg: versions and URLs of external recipe dependencies


  • lucicfg - CLI tool to generate the configuration from the starlark scripts. To install, clone depot_tools.
  • python - Python 3, used to execute recipes.

Imporant commands

Regenerate config data after making changes (lucicfg):

$ ./

Run recipe tests (python):

$ recipes/ test run

Update recipe test goldens (python):

$ recipes/ test train