← Back to team overview

canonical-ci-engineering team mailing list archive

Re: Touch Device Testing with a Readonly Image Issue

 

Right, but I expect this to change over time to the point where most
if not all of the apps will be click. We should be able to test these
in read-only mode and only use a writable image when testing those
packages that require it due to debian packaging.

On Fri, Apr 18, 2014 at 11:48 AM, Paul Larson <paul.larson@xxxxxxxxxxxxx> wrote:
> We also require a writable image because many of the upstream are
> installed via packages rather than clicks and require testsuites that
> come in as debian packages as well.
>
> On Thu, Apr 17, 2014 at 10:25 AM, Francis Ginther
> <francis.ginther@xxxxxxxxxxxxx> wrote:
>> As discussed in today's standup, we encountered a testing issue late
>> in the release cycle that was masked by the unlock_screen script. That
>> script currently requires installation of the unity8-autopilot package
>> which thus requires putting the phone into writable mode. As a result,
>> we have no testing on the device while the image is in read-only mode.
>>
>> As we're pushing toward an improved solution to unlocking the screen,
>> I want to make sure that doing so on a read-only image is a
>> requirement.
>>
>> 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



-- 
Francis Ginther
Canonical - Ubuntu Engineering - Continuous Integration Team


References