I've seen this more than once today on https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester:

we'll be running TabStripTests on the devices, then some or all of them will fail almost simultaneously:

W  233.694s TimeoutThread-1-for-run_tests_on_device(0b042e6e)  exit status of shell command '( p=org.chromium.chrome.tests;am instrument -w -r -e class \'org.chromium.chrome.browser.compositor.overlays.strip.TabStripTest#testScrollingStripStackerScrollsToSelectedTab\' "$p"/org.chromium.chrome.test.ChromeInstrumentationTestRunner )>/data/local/tmp/temp_file-b5e5469b21e5' missing.
W  233.694s TimeoutThread-1-for-run_tests_on_device(0b062ec0)  exit status of shell command '( p=org.chromium.chrome.tests;am instrument -w -r -e class \'org.chromium.chrome.browser.compositor.overlays.strip.TabStripTest#testSwitchStripStackersWithIncognito\' "$p"/org.chromium.chrome.test.ChromeInstrumentationTestRunner )>/data/local/tmp/temp_file-34ca59c48a193' missing.
W  233.696s TimeoutThread-1-for-run_tests_on_device(09078485)  exit status of shell command '( p=org.chromium.chrome.tests;am instrument -w -r -e class \'org.chromium.chrome.browser.compositor.overlays.strip.TabStripTest#testScrollingStripStackerFadeOpacity\' "$p"/org.chromium.chrome.test.ChromeInstrumentationTestRunner )>/data/local/tmp/temp_file-3f0adab451611' missing.
W  233.696s TimeoutThread-1-for-run_tests_on_device(0b03b29d)  exit status of shell command '( p=org.chromium.chrome.tests;am instrument -w -r -e class \'org.chromium.chrome.browser.compositor.overlays.strip.TabStripTest#testSwitchStripStackersWithMiddleTabSelected\' "$p"/org.chromium.chrome.test.ChromeInstrumentationTestRunner )>/data/local/tmp/temp_file-627bbd99db2cf' missing.
W  233.697s TimeoutThread-1-for-run_tests_on_device(0af6646d)  exit status of shell command '( p=org.chromium.chrome.tests;am instrument -w -r -e class \'org.chromium.chrome.browser.compositor.overlays.strip.TabStripTest#testScrollingStripStackerTabOffsets\' "$p"/org.chromium.chrome.test.ChromeInstrumentationTestRunner )>/data/local/tmp/temp_file-929e844e26b2c' missing.
W  233.697s TimeoutThread-1-for-run_tests_on_device(0a294402)  exit status of shell command '( p=org.chromium.chrome.tests;am instrument -w -r -e class \'org.chromium.chrome.browser.compositor.overlays.strip.TabStripTest#testSwitchStripStackersWithFirstTabSelected\' "$p"/org.chromium.chrome.test.ChromeInstrumentationTestRunner )>/data/local/tmp/temp_file-3b4f335cc069e' missing.
W  233.698s TimeoutThread-1-for-run_tests_on_device(0a084b87)  exit status of shell command '( p=org.chromium.chrome.tests;am instrument -w -r -e class \'org.chromium.chrome.browser.compositor.overlays.strip.TabStripTest#testSwitchStripStackersWithLastTabSelected\' "$p"/org.chromium.chrome.test.ChromeInstrumentationTestRunner )>/data/local/tmp/temp_file-ca80138f813fb' missing.

the devices are subsequently not adb visible.

e.g.

https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/5520 (all devices died)
https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/5524 (all devices died, but one came back in time to not get blacklisted)

I would typically chalk this up to adb being weird, but in both cases it happened with the TabStripTests running on all devices...


+cc changwan & dtrainor as closest OWNERS: ever seen anything like this from the TabStripTests?