More detail on Edgar failure:

08/01 17:02:02.252 INFO |hardware_StorageWe:0085| Found eMMC version 5.1
08/01 17:02:02.264 DEBUG|        base_utils:0176| Running 'logger "autotest finished iteration /usr/local/autotest/results/default/hardware_StorageWearoutDetect/sysinfo/iteration.1"'
08/01 17:02:02.274 WARNI|              test:0606| Autotest caught exception when running test:
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 804, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 461, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 376, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/hardware_StorageWearoutDetect/hardware_StorageWearoutDetect.py", line 102, in run_once
    raise error.TestFail(msg)
TestFail: Detected wearout parameter:MMC failure DEVICE_LIFE_TIME_EST_TYP_A


log : https://00e9e64bac0106cbb4e0108f3b8d520e747f44ad4c89ad0b32-apidata.googleusercontent.com/download/storage/v1_internal/b/chromeos-autotest-results/o/71759223-gkihumba%2Fchromeos4-row12-rack7-host1%2Fdebug%2Fclient.0.DEBUG?qk=AD5uMEsMxS2FkZEh4TK7JYvsKGIxiQK5_enyPvWs5fHF6veAWpr0xlaGxMC_OgTEmdL4g6scU0pguanWchZY8jBHODy0Bmk9BxDGs2ifoT5YK69BLqOBHFc4oOOturYx-NLfUZHp9d9xfTEzbW_oaAEu3i887J-0OuALXsDcA8h5XPINpg0hNoDV1c4bpnLH6xbrG-1AlG2PgNRX6e_V4xDbum-1zUd2s8965QZxZnS3fd4M9uApMptKVVCM4Fvjz1xkmFDFXssTKOp7qIwWyOo9YqXvk-9B0KudUfGKWqb1Jib5PU8bys0ppPYSro5pbqjY3NkeZDQ_U09lg5hiQFAi2tUWsaNMQ7ZG8qRxIQjkKemHgAhYdIoPVXtrrXSLRxKDdKCAiRyQs0SktI9LxkAW9-IiU8RaGHzIgeDnf4s4YVqRyxM99Sgh16O1iA0puFIzO6ZrNY01PwjkwH8odyWevWiAQ-mVBRe-XV4LaxTTDpNfZL9o26JILdWfIHLt_i3n5GN11OOifKYsiWR-SsxJUZeqYKug5O51VDDMjlicI-C8Fbksq-DjPrPv7wazUDu4GFbke2dKfjTmsbJ2sYv4HdRqHTKxCabfuJFWG6rRoqn0CT8Cht5GoLerhAq7db774EraomlR6FMjH8Tv9sVDRGOKTB1J3wvjn274jWHi_yJ7Bi8v-RSJxcIQcBUgByJoxTSb_waNzR0v0mPNZl8QcZtSq-JI25Ha4D5nn5gdQP9YMoiUSima8nL_5YmvGkht11MeuS08mHm1DtjMzChgTm1S4W3D-z88HQp1WYYxH5V0DzokDXqADwMlUCR8HAGCIVdeystzlYnsnMoXylB48uVPJenGabnOn9M7bYA0oVwvqNxkCxluP1xd4uOqfhJuhm5_T3_8FGeRBtcJspuLsKEgDwxtC0TXToxmtxtefKdGMZy4c2I

the top level links 

edgar: https://uberchromeos-server38.corp.google.com/new_tko/#tab_id=spreadsheet_view&row=job_name%252Ctest_name&column=status&show_incomplete=true&show_only_latest=false&show_invalid=true&condition=job_name%2520LIKE%2520%27edgar-release/R52-8350.66.0/bvt-cq/%2525%27%2520AND%2520test_name%2520%253C%253E%2520%27SERVER_JOB%27%2520AND%2520test_name%2520NOT%2520LIKE%2520%27CLIENT%255C_JOB%2525%27

mighty:  https://uberchromeos-server38.corp.google.com/new_tko/#tab_id=spreadsheet_view&row=job_name%252Ctest_name&column=status&show_incomplete=true&show_only_latest=false&show_invalid=true&condition=job_name%2520LIKE%2520%27veyron%255C_mighty-release/R52-8350.67.0/bvt-cq/%2525%27%2520AND%2520test_name%2520%253C%253E%2520%27SERVER_JOB%27%2520AND%2520test_name%2520NOT%2520LIKE%2520%27CLIENT%255C_JOB%2525%27

scroll down to view hardware_StorageWearoutDetect failures.

If you're sure about bad hw, please file a bug at go/cros-lab-device-repair and reference this bug.

Is this process documented anywhere for sheriffs?

I'm not sure about the bad hardware, but this test keeps failing. Someone in the hardware lab would have to verify.

b/ issue at https://b.corp.google.com/u/0/issues/30771758

> Some hardware in the lab may need to be replaced as the above
> bvt-cq test keeps failing.

This test shouldn't be running in the 'bvt-cq' suite in the first
place.  In the latest branches, it's been moved to bvt-perbuild.
Only M52 still runs it in bvt-cq.  We should merge that change
back to M52.

We're almost done with M52 stable releases, just one more build next week. Please add merge request label so we can land this before next week.

Already merged under separate cover, see bug 589344.

Bulk closing Infra>Client>ChromeOS issues untouched in over a year.