Android test harness flakily fails to "list tests on any device" |
|||||
Issue descriptionSee https://chromium-swarm.appspot.com/task?id=365b656bb28b1e10 for an example failure. These types of failures will become more disruptive as android tests on the CQ begin to run on bots with only a single device as opposed to a batch of 4-7 that act as a fallback which mask the failure.
,
May 26 2017
,
May 30 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ff92c651176399f09eba023b4b0a1c1fa6dd36e6 commit ff92c651176399f09eba023b4b0a1c1fa6dd36e6 Author: John Budorick <jbudorick@chromium.org> Date: Tue May 30 19:17:24 2017 [android] Add more logging to help diagnose empty --gtest_list_tests output. Bug: 726880 Change-Id: Ib38b8322e2c38f0a14dda79149fdbd11025efd17 Reviewed-on: https://chromium-review.googlesource.com/517419 Reviewed-by: Benjamin Pastene <bpastene@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#475626} [modify] https://crrev.com/ff92c651176399f09eba023b4b0a1c1fa6dd36e6/build/android/pylib/local/device/local_device_gtest_run.py [modify] https://crrev.com/ff92c651176399f09eba023b4b0a1c1fa6dd36e6/testing/android/native_test/native_test_launcher.cc
,
Oct 20 2017
Issue 776950 has been merged into this issue.
,
Oct 20 2017
,
Nov 3 2017
I have some ideas how to debug this.
,
Nov 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/catapult/+/e44ea91e306e26efdd1130e1cb95a98459b03515 commit e44ea91e306e26efdd1130e1cb95a98459b03515 Author: Benjamin Pastene <bpastene@chromium.org> Date: Sat Nov 04 00:03:43 2017 devil: Add a device_utils method for taking a bugreport. It's pretty dumb, but it seems to work. I'll look into hooking this into result_details after it lands. Bug: chromium:726880 Change-Id: I458a36423d993aed58ab8af3a14d97cd8cb4c881 Reviewed-on: https://chromium-review.googlesource.com/752751 Commit-Queue: Benjamin Pastene <bpastene@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> [modify] https://crrev.com/e44ea91e306e26efdd1130e1cb95a98459b03515/devil/devil/android/device_utils.py
,
Nov 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/013dbb36ef317814daa42da0605d9be98ec5ebf5 commit 013dbb36ef317814daa42da0605d9be98ec5ebf5 Author: Benjamin Pastene <bpastene@chromium.org> Date: Wed Nov 29 22:40:28 2017 android: Retry test listing on devices when nothing is returned. Bug: 726880 Change-Id: If4d630ff8dc921fe59a306c4b7d1d2844bbab742 Reviewed-on: https://chromium-review.googlesource.com/794993 Commit-Queue: Benjamin Pastene <bpastene@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#520279} [modify] https://crrev.com/013dbb36ef317814daa42da0605d9be98ec5ebf5/build/android/pylib/local/device/local_device_gtest_run.py
,
May 25 2018
Have we seen this recently? I'm not sure we have. Then again I haven't been looking too hard... |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bpastene@chromium.org
, May 26 2017