[Webkit-unassigned] [Bug 96471] [chromium] When running layout tests on android judge about installation success from adb command exit status

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=96471





--- Comment #9 from Peter Beverloo <peter at chromium.org>  2012-09-14 06:44:20 PST ---
(In reply to comment #6)
> adb --version 2>&1 | head -1
> Android Debug Bridge version 1.0.29
> 
> As I wrote (see result of `which adb`), the adb is coming from the Android SDK that is in the chrome tree (pulled via git deps).
> 
> Could it be that the environment is set up differently? I am out of ideas.
> 
> If there are two valid adb modes with said behavior we would become more careful:
> 1. check if we encountered "Success" or "Failure" (we are with the "old" adb mode)
> 2. else judge by the exit code (we are with the adb mode that Egor is having)
> 
> I don't like how it looks/reads but really I do not see other ways how this can be transitioned from one mode to another smoothly given the assumption that two modes of adb are correct.

I have no idea why this is happening, maybe adb is crashing? Could you try to run adb in gdb to see if you get any crash stacks or other output? It seems very unlikely that ADB has a verbose and non-verbose mode, I fairly sure that's the case.

Other test suites in Chromium also check for "Success" in the command's output, so you should be able to rely on that. I suspect communication with the device may be timing out as well, have you tried reconnecting it, or using a different USB cable?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.