Chrome OS Version: 8872.67.0

Situation: I was running CTS on moblab and when it finished many jobs showed as aborted. The first job that showed aborted actually started to run but then seemed to hang and eventually time out. The other jobs after that simply aborted immediately without running presumably because of being in the queue too long.

It would be useful if the "Aborted" job status could distinguish between queue time out and the test being aborted in the middle. Could introduce more job states to accommodate the distinction and/or add another field to put further status details/clarification into. e.g.: Status: Aborted, Status Reason: Queue timed out.

As the autotest infrastructure is doing the aborting it should know the reason why, so it would be nice to surface it. Otherwise, some log file forensics is needed.