After I marked https://crrev.com/c/807753 (and two other dependent changes) ready, I got a bunch of errors like this from the commit bot:

---

The betty-pre-cq trybot for your change timed out after 240 minutes.

This problem can happen if your change causes the builder to hang, or if there is some infrastructure issue. If your change is not at fault you may mark your change as ready again. If this problem occurs multiple times please notify the sheriff and file a bug.

Commit queue documentation: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium-os/commit-queue-overview

---

Please update this message to include a link to the failed pre_cq run -- there's basically no way for the change author to determine whether the failure was their change's fault or not otherwise. The timestamps at https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/pre_cq/ don't appear to match up with the Gerrit messages, and the only way I've found to debug this is by sending by marking my change ready again and reloading the build list until I see the next run show up.
 

After I marked https://crrev.com/c/807753 (and two other dependent changes) ready, I got a bunch of errors like this from the commit bot:

---

The betty-pre-cq trybot for your change timed out after 240 minutes.

This problem can happen if your change causes the builder to hang, or if there is some infrastructure issue. If your change is not at fault you may mark your change as ready again. If this problem occurs multiple times please notify the sheriff and file a bug.

Commit queue documentation: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium-os/commit-queue-overview

---

Please update this message to include a link to the failed pre_cq run -- there's basically no way for the change author to determine whether the failure was their change's fault or not otherwise. The timestamps at https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/pre_cq/ don't appear to match up with the Gerrit messages, and the only way I've found to debug this is by marking my change ready again and reloading the build list until I see the next run show up.