I took a look at the latest failure  https://uberchromegw.corp.google.com/i/chromeos/builders/reks-release/builds/862, the HWtest timed out based on https://uberchromegw.corp.google.com/i/chromeos/builders/reks-release/builds/862/steps/HWTest%20%5Bsanity%5D/logs/stdio

Will return from run_suite with status: OK
13:36:27: INFO: RunCommand: /b/cbuild/internal_master/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /tmp/cbuildbot-tmpJwQIA7/tmpwhgM2b/temp_summary.json --raw-cmd --task-name reks-release/R58-9293.0.0-sanity --dimension os Ubuntu-14.04 --dimension pool default --print-status-updates --timeout 14400 --io-timeout 14400 --hard-timeout 14400 --expiration 1200 '--tags=priority:Build' '--tags=suite:sanity' '--tags=build:reks-release/R58-9293.0.0' '--tags=task_name:reks-release/R58-9293.0.0-sanity' '--tags=board:reks' -- /usr/local/autotest/site_utils/run_suite.py --build reks-release/R58-9293.0.0 --board reks --suite_name sanity --pool bvt --num 1 --file_bugs True --priority Build --timeout_mins 180 --retry True --max_retries 10 --minimum_duts 1 --suite_min_duts 1 --offload_failures_only False -m 101822445
16:00:28: WARNING: Killing tasks: [<_BackgroundTask(_BackgroundTask-7:7:2, started)>]
16:00:28: WARNING: Killing 21143 (sig=24 SIGXCPU)


looks like 2.5 hours trying to run swarming.py ? and test finally aborted http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=101822445

still fail, +current sheriff, infra and planner

reks-release on canary has been green since yesterday:
    https://uberchromegw.corp.google.com/i/chromeos/builders/reks-release

I didn't check whether R57 is still affected.

green since 2/20 for M58 and 2/18 for M57