OK - for the moment, I've off-lined 04. Longer term we need a better solution.
I think that the problem is that adb is buggy. It is clearly *supposed* to work with multiple devices simultaneously, otherwise why have it running as a daemon?
Course of action:
* We can patch around it by having an "android" device tag, which will be guaranteed to only have one instance per LAVA worker node.
* We should also investigate if there is an adb update that fixes the simultaneous connection issue.
Thanks
Dave
Its okay to have multiple models per machine but we need to have only one model running Android per machine which has proven to be stable. If we run Android on more than one model per machine then it results in adb errors. Hence Yongqin requested to take _04 offline.
Currently juice is the only project where Android is booted extensively on "rtsm_fvp_base-aemv8a" models. It is preferred to have only one such model per H/W instance to have the setup stable for Android.
Regards,
Vishal
_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation