I got several messages like the one below re: https://chrome-internal-review.googlesource.com/363432 and other dependent CLs.
----
The daisy_spring-no-vmtest-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.
----
I have no idea how to find the logs or other information which may help figure out if the problem is in my CLs, or with the infrastructure. (I don't think the problem is in the CLs---they are changing kernel code which is exercised only under heavy memory pressure, and changes the behavior in a relatively minor way.)
Comment 1 by akes...@chromium.org
, Jun 12 2017Labels: Hotlist-Fixit
Owner: nxia@chromium.org