ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #07471
Re: [Canonical-ci-engineering] Mako testing grinding to a halt with image 274
This is now reproducible for me using a simple script like:
for i in `seq 1 1000`; do
echo "LOOP $i"
adb reboot
adb wait-for-device
sleep 10
done
Sometimes it will make it through quite a few loops before failing.
One time I ran it, it only got through 3 loops before getting stuck.
I've also noticed that in many of the jobs where the device
disappears, it's getting stuck in a similar patter of adb reboot
followed by adb wait-for-device.
Thanks,
Paul Larson
On Wed, Apr 2, 2014 at 5:28 PM, Francis Ginther
<francis.ginther@xxxxxxxxxxxxx> wrote:
> 3 of the 4 mako devices servicing MP test requests on s-jenkins are
> unusable now. I suspect the 4th will meet a similar fate before a
> human is able to make it to the lab and recover the devices. The makos
> used by q-jenkins for the daily smoke tests are also becoming unusable
> and we'll likely see more devices fail before they can all be
> recovered.
>
> These issues started with image 274 and appear to occur during an adb
> reboot. It doesn't happen every time of course, but these devices are
> likely rebooted a dozen times per hour. When the issues occurs, a
> re-flash is needed.
>
> There are a couple of volunteers putting devices in a reboot loop to
> gather more info, but this is all I have at this time.
>
> Francis
> --
> Francis Ginther
> Canonical - Ubuntu Engineering - Continuous Integration Team
>
> --
> Mailing list: https://launchpad.net/~canonical-ci-engineering
> Post to : canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~canonical-ci-engineering
> More help : https://help.launchpad.net/ListHelp
Follow ups
References