canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

I'm generally all for quick fixes, but that sounds like a recipe for
further problems. Can we isolate one of these phones the next time
this happens, create a bug, and ask the phonedations team to have a
look?

If that sounds sensible, should we add that to the Vanguard project or Playbook?

On 5 December 2013 11:39, Para Siva <para.siva@xxxxxxxxxxxxx> wrote:
> On 05/12/13 07:27, Paul Larson wrote:
>>
>> The maguro we use for daily smoke testing (maguro-01) is visible, but
>> marked offline in adb even after the adb restart. Rick, can you take a
>> look at this one? At least we have it down to a single device (I
>> hope).  So we don't have maguro results.
>
>
> The smoke on maguro is now on maguro-02 and appears progressing.
>
> AFAIK this adb issue in kinnara is the second in three weeks. I am curious
> if we could run a cron job to restart adb  at a quiet time every day and/or
> killing very old adb processes to minimise this?
>
> Thanks
>
>
>
>
>
>
> --
> 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