General information about the Android compile server is available in the README.
The number of waiting compile tasks on Android Compile Server is too long. Take a look at the pending tasks here and here. Try to determine if the backends listed here are still running in skia-corp. Pending tasks can also be deleted if absolutely necessary here.
The mirror sync failed. This will likely cause all checkouts of the affected backend to also fail when syncing from the mirror.
Try syncing the mirrors again here.
If things still fail then try to log into the backend instance on skia-corp and run:
At least one backend of the Android Compile Bot thinks that the android tree is broken and is allowing Skia CLs to pass because the withpatch and nopatch builds are both red. Verify that the tree is really broken by looking at the android dashboard here. If it is not broken then look at task logs in the datastore here to see if it is only affecting one backend (look for NoPatchLog to exist and NoPatchSucceeded to be false). If it is only affecting one backend then try syncing the mirrors again here.
If nothing else works then make the bot an experimental bot in commit-queue.cfg and inform the Skia chat so developers are cautious with potentially breaking changes. Also contact the robocop with the contents of the failing NoPatchLog.
At least one checkout is failing to sync. Look at task logs in the datastore here to see if it is only affecting one backend (look for NoPatchLog to exist and NoPatchSucceeded to be false). If it is only affecting one backend then try syncing the mirrors again here.
If nothing else works then make the bot an experimental bot in commit-queue.cfg and inform the Skia chat so developers are cautious with potentially breaking changes. Also contact the robocop with the contents of the failing NoPatchLog.