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.
The frontend server is taking too long to respond. Check the logs for any obvious cause; if load is high, we may need to bring up more replicas.
The AutoRoll server on the given host is logging errors at a higher-than-normal rate. This warrants investigation in the logs. The most common cause of this alert is transient errors while communicating with Git or Gerrit. In that case, there is not much which can be done other than to silence the alert and hope that things improve. If the failure persists, contact the current on-call for the Git service.
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. Inform the Skia sheriff that the Skia->Flutter roller is failing the license script and that you are investigating.
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). Sometimes a typo in license headers 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:
Some issue is preventing the roller from running normally. You'll need to look through the logs for more information. Normally this is transient, but it can also be caused by mis-configuration of the roller, eg. the configured reviewer is not a committer.
Setting the roller mode to “Stopped” should be enough in most cases. If not, you can use
kubectl delete -f <file> to kill it.