[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-test-cases Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/b

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread Francis Ginther
The jenkins job was indeed hardcoded to use image 276 due to an unbootable image at 277. We then failed to remove this once the image was fixed. Image 311 is working and unlock is successful: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily- mako/421/consoleFull [log snippet] I

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread Michał Sawicz
I just tried following http://ubuntu-test-cases- touch.readthedocs.org/en/latest/ on mako with devel-proposed: $> IMAGE_OPT="--bootstrap --developer-mode --channel=ubuntu-touch/devel-proposed" ./scripts/provision.sh -w FLASHING DEVICE Attempting adb reboot bootloader === Device in fastboo

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread Michał Sawicz
I just noticed: + export REVISION=--revision=276 [...] 2015/09/22 12:38:36 Flashing version 276 from ubuntu-touch/devel-proposed/ubuntu channel and server https://system-image.ubuntu.com to device mako The job seems hardcoded on image 276 for some reason, when we're at 311 already, and that's w

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread Michał Sawicz
The above log suggests it's not the tool that's failing, but rather the shell environment isn't complete - i.e. dbus and upstart details are not available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. http

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread kevin gunn
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Josh Arenson (josharenson) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1498541 Title: Automated screen unlo

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread kevin gunn
** Changed in: unity8 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1498541 Title: Automated screen unlock not working on wily im

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

2015-09-22 Thread Francis Ginther
** Attachment added: "Full console log from failing CI build." https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1498541/+attachment/4471433/+files/unlock-fails-consoleText.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscri