Forwarder is crashing on Chromedriver android bot |
||||
Issue descriptionhttps://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/36314 Traceback (most recent call last): File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/chrome/test/chromedriver/test/run_py_tests.py", line 2625, in <module> ChromeDriverTest.GlobalTearDown() File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/chrome/test/chromedriver/test/run_py_tests.py", line 348, in GlobalTearDown forwarder.Forwarder.UnmapAllDevicePorts(ChromeDriverTest._device) File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/third_party/catapult/devil/devil/android/forwarder.py", line 227, in UnmapAllDevicePorts raise HostForwarderError('\n'.join(error_msg)) devil.android.forwarder.HostForwarderError: `/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/forwarder_host --adb=/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/third_party/android_tools/sdk/platform-tools/adb --serial-id=0757a2f000599749 --unmap-all` exited with -6 [0920/073405.231050:FATAL:host_forwarder_main.cc(145)] Check failed: bytes_read > 0 (0 vs. 0) #0 0x000000486c47 base::debug::StackTrace::StackTrace() #1 0x0000004721c1 logging::LogMessage::~LogMessage() #2 0x000000409113 forwarder2::(anonymous namespace)::ClientDelegate::OnDaemonReady() #3 0x00000040a8ff forwarder2::Daemon::SpawnIfNeeded() #4 0x000000408ab6 main #5 0x7f8420b00ec5 __libc_start_main #6 0x000000408569 <unknown> Can someone please look into it?
,
Sep 20 2017
Haven't seen a forwarder bug in a while. I'll look at this in a bit.
,
Sep 20 2017
Reverting the CL that updated the devil forwarder binary.
,
Sep 21 2017
Working again after the revert rolled into chromium. Sorry about the disruption.
,
Sep 21 2017
Thanks for fixing it :) |
||||
►
Sign in to add a comment |
||||
Comment 1 by gmanikpure@chromium.org
, Sep 20 2017