many jobs were aborted in the canary builds this morning.

https://uberchromegw.corp.google.com/i/chromeos/builders/asuka-release/builds/1982

http://cros-full-0012.mtv.corp.google.com/afe/#tab_id=view_job&object_id=179757922

there's no gs logs for this aborted job, and the only log I found in the shard is 

"chromeos-test@cros-full-0012:/usr/local/autotest/logs$ grep 179757922 scheduler.log.2018-02-27-04.00.21 
02/27 08:28:06.489 INFO |        monitor_db:1068| Aborting HQE: 180179721, for job: 179757922 and host: no host has status:Queued [aborted]
02/27 08:28:06.490 INFO |  scheduler_models:0641| HQE: 180179721, for job: 179757922 and host: no host has status:Queued [aborted] -> Aborted
"

The other jobs (except aborted jobs) completed successfully before 06:12:20 and the suite was aborted at  08:27:07


+ ayatane@ / pprabhu@, any ideas about what happened to the aborted jobs? can we turn on more logs in the scheduler?