The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ac7102616f736bc0e527eb577063f5077a982c6c

commit ac7102616f736bc0e527eb577063f5077a982c6c
Author: Ned Nguyen <nednguyen@google.com>
Date: Fri May 26 22:41:50 2017

Deschedule benchmarks on 'build75-b1--device1'

Device "build75-b1--device1" is blacklisted. These benchmarks are not scheduled:
 * loading.mobile
 * loading.mobile.reference
 * media.android.tough_video_cases_tbmv2
 * media.android.tough_video_cases_tbmv2.reference
 * service_worker.service_worker
 * service_worker.service_worker.reference
 * smoothness.tough_webgl_ad_cases
 * smoothness.tough_webgl_ad_cases.reference

TBR=charliea@chromium.org, benhenry@chromium.org
NOTRY=true

Bug:  726874 
Change-Id: I5c081b877ac993d4f7a478eac783be41a1e3b283
Reviewed-on: https://chromium-review.googlesource.com/517622
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#475167}
[modify] https://crrev.com/ac7102616f736bc0e527eb577063f5077a982c6c/testing/buildbot/chromium.perf.json
[modify] https://crrev.com/ac7102616f736bc0e527eb577063f5077a982c6c/tools/perf/core/perf_data_generator.py

https://chromium-swarm.appspot.com/bot?id=build75-b1--device1 seems fine. What about it is broken?

I recall that swarming was reporting this device dead when I filed the bug. I will try to reschedule benchmarks on it to see what happen now.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c63a92c68096fa2922990bf76169203263a88dab

commit c63a92c68096fa2922990bf76169203263a88dab
Author: Ned Nguyen <nednguyen@google.com>
Date: Tue May 30 17:31:08 2017

Revert "Deschedule benchmarks on 'build75-b1--device1'"

This reverts commit ac7102616f736bc0e527eb577063f5077a982c6c.

Reason for revert: 'build75-b1--device1' is online again

NOTRY=true
Original change's description:
> Deschedule benchmarks on 'build75-b1--device1'
> 
> Device "build75-b1--device1" is blacklisted. These benchmarks are not scheduled:
>  * loading.mobile
>  * loading.mobile.reference
>  * media.android.tough_video_cases_tbmv2
>  * media.android.tough_video_cases_tbmv2.reference
>  * service_worker.service_worker
>  * service_worker.service_worker.reference
>  * smoothness.tough_webgl_ad_cases
>  * smoothness.tough_webgl_ad_cases.reference
> 
> TBR=charliea@chromium.org, benhenry@chromium.org
> NOTRY=true
> 
> Bug:  726874 
> Change-Id: I5c081b877ac993d4f7a478eac783be41a1e3b283
> Reviewed-on: https://chromium-review.googlesource.com/517622
> Reviewed-by: Ned Nguyen <nednguyen@google.com>
> Commit-Queue: Ned Nguyen <nednguyen@google.com>
> Commit-Queue: Stephen Martinis <martiniss@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#475167}

TBR=nednguyen@google.com,martiniss@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug:  726874 

Change-Id: I70bccbfaf459448ee4e9677c8d2de133d2143a0f
Reviewed-on: https://chromium-review.googlesource.com/518265
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#475580}
[modify] https://crrev.com/c63a92c68096fa2922990bf76169203263a88dab/testing/buildbot/chromium.perf.json
[modify] https://crrev.com/c63a92c68096fa2922990bf76169203263a88dab/tools/perf/core/perf_data_generator.py

Some one-device bots may appear dead temporarily. (That's when the host wants to reboot, so it sends a sigkill to all local swarming bots and waits for them to finish running their tests before rebooting.) As long as it hasn't been dead for more than a couple hours, it's probably fine.

Thanks Ben for the info.