New issue
Advanced search Search tips

Issue 788859 link

Starred by 1 user
Status: WontFix
Owner:
bpastene@chromium.org
Closed: Mar 2018
Cc:
bpastene@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

net_unittests failing on chromium.android/KitKat Phone Tester (dbg)

Project Member Reported by ntfschr@chromium.org, Nov 27 2017 
net_unittests failing on chromium.android/KitKat Phone Tester (dbg)

Builders failed on: 
- KitKat Phone Tester (dbg): 
  https://build.chromium.org/p/chromium.android/builders/KitKat%20Phone%20Tester%20%28dbg%29

---

Maybe this is a swarming issue? Shard #2 failed, I think the relevant exception is:

  File "/b/swarming/w/ir/third_party/catapult/devil/devil/utils/reraiser_thread.py", line 81, in run
    self._ret = self._func(*self._args, **self._kwargs)
  File "/b/swarming/w/ir/build/android/pylib/local/device/local_device_environment.py", line 77, in wrapper
    on_failure(dev, f.__name__)
  File "/b/swarming/w/ir/build/android/pylib/local/device/local_device_environment.py", line 261, in BlacklistDevice
    'All devices were blacklisted due to errors')
NoDevicesError: All devices were blacklisted due to errors

Comment 1 by bpastene@chromium.org, Nov 27 2017

Owner: bpastene@chromium.org
Status: Assigned (was: Untriaged)
The device was blacklisted because the forwarder on the host had trouble quitting:
I   26.627s individual_device_set_up(06b21999f0e94e51)  [host]> /b/swarming/w/ir/out/Debug/host_forwarder --kill-server
W   29.077s individual_device_set_up(06b21999f0e94e51)  Forwarder unable to shut down:
[1127/200003.901364:ERROR:daemon.cc(260)] Timed out while killing daemon. It might still be tearing down.

I   29.077s individual_device_set_up(06b21999f0e94e51)  [host]> pkill -9 host_forwarder



Looks like it was just a flake. Though, we probably shouldn't be bubbling that up as a device error. I'll see if I can make things clearer.

Comment 2 by hbos@chromium.org, Nov 28 2017

Labels: -Pri-2 Infra-Troopers Pri-1
Still happening:
https://build.chromium.org/p/chromium.android/builders/KitKat%20Phone%20Tester%20%28dbg%29/builds/1453
With "NoDevicesError: All devices were blacklisted due to errors"

Here's another one:
https://build.chromium.org/p/chromium.android/builders/KitKat%20Phone%20Tester%20%28dbg%29/builds/1459
That one instead saying "CommandFailedError: Failed to list tests on any device"

Device issues - is this an infra problem? Adding Infra-Troopers, feel free to remove if inappropriate.
Normally I would disable the test so I can remove it from the sheriff bug queue, but I don't think we should disable an entire binary.

Comment 3 by bpastene@chromium.org, Nov 28 2017 

Thanks for the reports. Looks like this forwarder problem is pretty flakey, I'll get to that eventually.

And that 2nd failure is  bug 726880 . Also an infra issue. Also flakey. Also on my plate.

Comment 4 by jbudorick@chromium.org, Dec 4 2017

Components: Infra>Client>Chrome
Moving Infra>Client>Android -> Infra>Client>Chrome+OS=Android

Comment 5 by jbudorick@chromium.org, Dec 4 2017

Components: -Infra>Client>Android

Comment 6 by pkasting@chromium.org, Dec 6 2017

Labels: -Sheriff-Chromium
It doesn't seem like there's anything sheriffs can or should do about this, so removing from the sheriff queue.

Comment 7 by bpastene@chromium.org, Mar 21 2018

Status: WontFix (was: Assigned)
Bot seems fine now? Feel free to reopen if that's not the case.
►

Sign in to add a comment