canonical-ci-engineering team mailing list archive
-
canonical-ci-engineering team
-
Mailing list archive
-
Message #01010
Re: Fwd: mir-mediumtests-runner-mako jobs have been disabled
C team and Francis,
Alberto has what looks like a fix and seems to work locally:
https://code.launchpad.net/~albaguirre/mir/fix-mircommon-symbols/+merge/244824
<https://code.launchpad.net/%7Ealbaguirre/mir/fix-mircommon-symbols/+merge/244824>
could someone test the affected job with this branch (and stand by to
fix things if it doesn't work)?
Alan
On 15/12/14 19:56, Cemil Azizoglu wrote:
>
> FYI
>
> ---------- Forwarded message ----------
> From: *Francis Ginther* <francis.ginther@xxxxxxxxxxxxx
> <mailto:francis.ginther@xxxxxxxxxxxxx>>
> Date: Mon, Dec 15, 2014 at 12:58 PM
> Subject: mir-mediumtests-runner-mako jobs have been disabled
> To: Kevin Gunn <kevin.gunn@xxxxxxxxxxxxx
> <mailto:kevin.gunn@xxxxxxxxxxxxx>>, Cemil Azizoglu
> <cemil.azizoglu@xxxxxxxxxxxxx <mailto:cemil.azizoglu@xxxxxxxxxxxxx>>,
> canonical-ci-engineering <canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx
> <mailto:canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx>>
>
> Kevin and C team,
>
> We've had to disable this job [1]. The execution of the job is causing
> the makos to be left in an unusable state. The problem occurs after
> the test and MP generated packages are installed and the phone
> reboots. After the reboot, the devices stay at the Google splash
> screen and never progress and adb is unusable.
>
> We've created a task [2] to add some automatic recovery as part of the
> job so that the jobs can be re-enabled. This is only meant to recover
> the devices once they are wedged, it does nothing to solve the source
> of the problem.
>
> [1] - http://s-jenkins.ubuntu-ci:8080/job/mir-mediumtests-runner-mako/
> [2] - https://app.asana.com/0/8736198969650/22345555555309
>
> Francis
> --
> Francis Ginther
> Canonical - Ubuntu Engineering - Continuous Integration Team
>
>
> --
> Cemil Azizoglu
> Mir Display Server - Team Lead
> Canonical USA
>
>
Follow ups
References