Looks like it's timing out (20 minutes) and getting aborted.

The child job didn't get a DUT to run on.

http://cautotest/afe/#tab_id=view_job&object_id=197412952

Perhaps all of the DUTs were occupied.

Until there's a more specific actionable problem there's not much else that can be done.

Should it not have waited one day for a free DUT and once it got the DUT ran at most 20 minutes? Otherwise this can be trivially worked around by increasing max_runtime from the test_that command line.

Timeout:	1440 minutes
Max runtime:	20 minutes

I started this yesterday afternoon.

How difficult is it to understand why I can't get a device?

$ test_that -i kevin-release/R68-10646.0.0 --max_runtime_mins 1440 -b kevin :lab: platform_MemoryPressure
INFO:root:About to start lab suite with command ['/mnt/host/source/src/third_party/autotest/files/site_utils/run_suite.py', '--board=kevin', '--build=kevin-release/R68-10646.0.0', '--model=', '--suite_name=test_that_wrapper', '--pool=suites', '--max_runtime_mins=1440', "--suite_args={'tests': ['platform_MemoryPressure']}"].
Autotest instance created: cautotest
05-07-2018 [17:05:46] Submitted create_suite_job rpc
05-07-2018 [17:05:51] Created suite job: http://cautotest/afe/#tab_id=view_job&object_id=198239106
@@@STEP_LINK@Link to suite@http://cautotest/afe/#tab_id=view_job&object_id=198239106@@@
The suite job has another 23:29:56.771139 till timeout.
The suite job has another 22:59:54.035448 till timeout.
The suite job has another 22:29:51.368487 till timeout.
The suite job has another 21:59:47.174777 till timeout.
The suite job has another 21:29:43.089289 till timeout.
The suite job has another 20:59:38.774931 till timeout.
The suite job has another 20:29:35.667813 till timeout.
The suite job has another 19:59:30.982002 till timeout.
The suite job has another 19:29:28.130987 till timeout.
The suite job has another 18:59:23.280040 till timeout.
The suite job has another 18:29:18.650665 till timeout.
The suite job has another 17:59:15.059587 till timeout.
The suite job has another 17:29:11.674936 till timeout.
The suite job has another 16:59:05.951905 till timeout.
The suite job has another 16:29:03.012300 till timeout.
The suite job has another 15:58:58.982043 till timeout.
The suite job has another 15:28:55.628319 till timeout.
The suite job has another 14:58:53.063504 till timeout.
The suite job has another 14:28:47.959308 till timeout.
The suite job has another 13:58:42.452484 till timeout.
The suite job has another 13:28:39.883928 till timeout.
The suite job has another 12:58:37.166361 till timeout.
The suite job has another 12:28:34.250867 till timeout.

05-08-2018 [05:06:00] printing summary of incomplete jobs (1):

platform_MemoryPressure: http://cautotest/afe/#tab_id=view_job&object_id=198239431
The suite job has another 11:58:30.311741 till timeout.
The suite job has another 11:28:27.469596 till timeout.
The suite job has another 10:58:24.498296 till timeout.
The suite job has another 10:28:22.167986 till timeout.
The suite job has another 9:58:18.968533 till timeout.
The suite job has another 9:28:16.539059 till timeout.
The suite job has another 8:58:13.118165 till timeout.
The suite job has another 8:28:09.606118 till timeout.
The suite job has another 7:58:06.814748 till timeout.
The suite job has another 7:28:01.595564 till timeout.
The suite job has another 6:57:58.809308 till timeout.
The suite job has another 6:27:56.047163 till timeout.
The suite job has another 5:57:53.484015 till timeout.
The suite job has another 5:27:50.200841 till timeout.

There are lots of jobs in the queue, but I don't think they are for pool:suites. And that pool did a lot of work of lower priority than yours, so it is not clear why it is ignoring your request.

It looks like the parent suite timed out, but the child jobs (actual tests) ran

This is the Friday attempts
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/197415495-ihf/chromeos6-row3-rack5-host17/
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/198239431-semenzato/chromeos6-row4-rack5-host14/platform_MemoryPressure/

Here are all the test runs so far
https://stainless.corp.google.com/search?test=%5Eplatform%5C_MemoryPressure%24&exclude_non_release=true&exclude_cts=true&col=build&row=board_model&view=matrix&first_date=2018-05-02&last_date=2018-05-08

Maybe the lab is just backed up a lot after last weeks outage?