I see a lot of failure when a job is aborted as soon as it is started:

For instance. in http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=109815318,
child security_SuidBinaries

03/30 11:49:21.669 INFO |        server_job:0184| START	----	link-paladin/R59-9415.0.0-rc1/bvt-inline/security_SuidBinaries	timestamp=1490899761	localtime=Mar 30 11:49:21	
03/30 11:49:21.670 INFO |        server_job:0184| 	ABORT	----	link-paladin/R59-9415.0.0-rc1/bvt-inline/security_SuidBinaries	timestamp=1490899761	localtime=Mar 30 11:49:21	
03/30 11:49:21.670 INFO |        server_job:0184| END ABORT	----	link-paladin/R59-9415.0.0-rc1/bvt-inline/security_SuidBinaries	timestamp=1490899761	localtime=Mar 30 11:49:21


I originally filed it under 674768, but it is not related to cyan.

Take also a look at http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=109819936
A suite with a single test that is aborted as soon as it is started, but the child test does complete.