This cave-paladin run failed:
    https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/15942

The test suite is here:
    http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=139334414

That test suite shows two runs of the security_ASLR test;
the first test attempt failed because of a provision failure;
the second passed:
    (failure) http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=139335853
    (success) http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=139336707

The provision failure _should_ have been recorded as a failure of
the security_ASLR, and the retry should then have been recorded as
a success.  Instead, the suite job's status.log shows this:

START	139335853-chromeos-test/chromeos2-row8-rack7-host18/provision_AutoUpdate	provision	timestamp=1504406806	localtime=Sep 02 19:46:46	
	FAIL	139335853-chromeos-test/chromeos2-row8-rack7-host18/provision_AutoUpdate	provision	timestamp=1504407273	localtime=Sep 02 19:54:33	Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row8-rack7-host18: SSHConnectionError: Connection to 100.115.231.15 timed out while waiting to read
END FAIL	139335853-chromeos-test/chromeos2-row8-rack7-host18/provision_AutoUpdate	provision	timestamp=1504407273	localtime=Sep 02 19:54:33	
START	139336707-chromeos-test/chromeos2-row8-rack7-host11/security_ASLR	security_ASLR	timestamp=1504407554	localtime=Sep 02 19:59:14	
	GOOD	139336707-chromeos-test/chromeos2-row8-rack7-host11/security_ASLR	security_ASLR	timestamp=1504407565	localtime=Sep 02 19:59:25	completed successfully
END GOOD	139336707-chromeos-test/chromeos2-row8-rack7-host11/security_ASLR	security_ASLR	timestamp=1504407565	localtime=Sep 02 19:59:25	

The first failure was recorded as a failure of provision_AutoUpdate,
not security_ASLR, so the suite failed, and the paladin run failed.