Hi botao,
Hi Amit,Yes, use the --disable-reboot probably is a good walk around, but since Google designed their test cases with a reboot as a pre-condition, then they must have their own purpose, like wipe cache or something else. So if we simply disable the reboot, perhaps it will affect the test result finally.@Naresh, I have no idea about the "workload" test suite requires a reboot or not. If the reboot is unnecessary for that test, then everything will be fine.@Vishal, would you provide the details of your solution in this condition? Run CTS test which requires reboot and using ADB over Ethernet as the connection?Thank you all.Best RegardsBotao SunOn Thu, Feb 21, 2013 at 10:46 PM, amit khare <amit.khare@linaro.org> wrote:
Try with --disable-reboot option-AmitOn 21 February 2013 17:07, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
+linaro.android+vishalOn 21 February 2013 16:39, Botao Sun <botao.sun@linaro.org> wrote:
Hi Amit & Soumya,Perhaps you have realised this issue, which means if our test target only supports ADB over Ethernet, then some CTS test cases won't be executed if they require a system reboot.As we know, in order to enable ADB over Ethernet, we need to do following 3 steps on our test target:stop adbdsetprop service.adb.tcp.port 6565start adbdSome CTS test (for example, "Android" test suite), will reboot system before being performed. Since the variable settings above will be lost after powered off, then after system rebooted, ADB over Ethernet connection will be lost. I tried this on vexpress A9 board and found many test cases couldn't be run just because the ADB connection failed after rebooting.Therefore, when run CTS, the test target should support ADB over USB connection, then can ensure everything goes well.I think we have way to solutions to fix adb issue on TCP connection as well. workload automation runs on vexpress+TC2 which use ADB connection over TCP. Vishal has already have a solution for this problem.Best regardsNaresh KambojuThanks.
Best RegardsBotao Sun