Consider this snippet of DUT history:
    2018-08-28 16:15:17  OK https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos2-row7-rack10-host17/1398689-provision/
    2018-08-28 16:13:44  OK https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos2-row7-rack10-host17/1398682-repair/
    2018-08-28 16:13:28  -- https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos2-row7-rack10-host17/1398680-reset/
    2018-08-28 15:52:32  -- https://stainless.corp.google.com/browse/chromeos-autotest-results/231672285-chromeos-test/
    2018-08-28 15:51:48  OK https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos2-row7-rack10-host17/1398574-reset/
    2018-08-28 15:46:26  -- https://stainless.corp.google.com/browse/chromeos-autotest-results/231670944-chromeos-test/

The logs show the following events:
15:46:26  test against arm64-llvm-next-toolchain/R70-11012.0.0-rc1
15:52:32  Paygen (AU) test against elm-release/R70-11013.0.0
16:13:28  Failed reset task; logs show this error message:
    cros-version label "cros-version:arm64-llvm-next-toolchain/R70-11012.0.0-rc1" does not match release_builder_path elm-release/R70-11013.0.0. Removing the label.

The Paygen test successfully installed elm-release/R70-11013.0.0, but
apparently never deleted or updated the cros-version label.  Instead,
reset for the next test found and fixed the problem.

Because of the failed reset, the device entered repair, found nothing
wrong (because the prior reset had fixed it), and then carried on,
resulting in a nearly 2-minute hiatus.