General information about the AutoRoller is available in the README.
The AutoRoller requires that gitcookies are in metadata under the key gitcookies_$INSTANCE_NAME.
The most recent DEPS roll attempt failed. This is usually due to a change in the child repo which is incompatible with the parent and requires some investigation into which bots failed and why. Fixing this usually requires a commit to the child repo, either a revert or a fix. This alert is only enabled for Skia.
There have been no successful rolls landed in the last 24 hours. This alert assumes that at least one commit has landed in the child repo in the last 24 hours; if that is not the case, then this alert can be safely ignored. This alert is only enabled for Skia.
One of the AutoRoll servers is taking too long to respond. The name of the prober which triggered the alert should indicate which roller is slow.
The AutoRoll server on the given host is logging errors at a higher-than-normal rate. This warrants investigation in the logs.
The state machine may throw errors like this: “Transition is already in progress; did a previous transition get interrupted?” That is intended to detect the case where we interrupted the process during a state transition, and we may be in an undefined state. This requires manual investigation, after which you should remove the /mnt/pd0/autoroll_workdir/state_machine_transitioning file. This error may also prevent the roller from starting up, which is by design.
If this happened on the Skia->Flutter roller then also take a look at the flutter_license_script_failure section below.
The Skia->Flutter roller has failed due to errors from Flutter's license script. Take a look at the cloud logs of the roller here. Failures due to license script errors typically look like this: “Failed to transition from “idle” to “active”: Error when running pre-upload step: Error when running dart license script: Command exited with exit status 1:”...
If the error looks related to Skia, then take a look at the recent unrolled changes to see if you can identify which change caused the license script to fail. Sometimes adding a new directory in third_party without a LICENSE file can cause the script to fail (example).
If you need to run the license scripts manually on a clean local checkout, then follow these steps-
Useful documentation links: