CI mako glitch

Daniel van Vugt daniel.van.vugt at canonical.com
Wed Sep 17 02:02:16 UTC 2014


Thanks Chris.

Can anyone remind me where/if we have access to change the CI scripting?

- Daniel


On 16/09/14 22:13, Chris Gagnon wrote:
> Make the image writable before using phablet-network.
>
> This is what I am using to reflash the mako phones I use for long
> running tests
>
> exec_with_adb() {
>      adb -s $ANDROID_SERIAL shell "echo 1234|sudo -S $@"
> }
>
> adb -s $ANDROID_SERIAL reboot-bootloader
> sudo ubuntu-device-flash --serial=$ANDROID_SERIAL
> --channel=devel-proposed --bootstrap --developer-mode --password=1234
>
> adb -s $ANDROID_SERIAL wait-for-device
> sleep 65
>
> phablet-config -s $ANDROID_SERIAL welcome-wizard --disable
> exec_with_adb 'touch /userdata/.writable_image'
> exec_with_adb 'reboot'
>
> sleep 10
> adb -s $ANDROID_SERIAL  wait-for-device
> sleep 65
> phablet-config -s $ANDROID_SERIAL edges-intro --disable
> phablet-network -s $ANDROID_SERIAL
>
> On Mon, Sep 15, 2014 at 11:58 PM, Daniel van Vugt
> <daniel.van.vugt at canonical.com <mailto:daniel.van.vugt at canonical.com>>
> wrote:
>
>     Does anyone know how to fix this? The CI failure is holding up a few
>     branches...
>
>     Traceback (most recent call last):
>        File "/usr/bin/phablet-config", line 327, in <module>
>          main()
>        File "/usr/bin/phablet-config", line 324, in main
>          args.func(adb, args)
>        File "/usr/bin/phablet-config", line 147, in _handle_writable_image
>          adb.wait_for_network()
>        File
>     "/usr/lib/python2.7/dist-__packages/phabletutils/device.__py", line
>     89, in wait_for_network
>          call(cmd)
>        File
>     "/usr/lib/python2.7/dist-__packages/phabletutils/device.__py", line
>     26, in call
>          subprocess.check_call(args, shell=True)
>        File "/usr/lib/python2.7/__subprocess.py", line 540, in check_call
>          raise CalledProcessError(retcode, cmd)
>     subprocess.CalledProcessError: Command 'phablet-network
>     --skip-setup' returned non-zero exit status 124
>
>



More information about the Mir-devel mailing list