lp:~psivaa/ubuntu-test-cases/touch

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

87. By Para Siva on 2013-10-22

reverting production and staging changes for devel->trusty

86. By Para Siva on 2013-10-22

Changing to trusty proposed

85. By Andy Doan on 2013-10-21

fix issue in unlock_screen.sh and powerd-cli

We've been shifting around where powerd-cli is called. revno 77
moved the call into unlock_screen.sh. The problem is that the adb-shell
on the target won't exit until the two powerd-cli pids are killed. This
kills them once the screen is unlocked. Based on my testing this seems
to be adequate for ensuring the screen is on while the autopilot tests
are executed.

84. By Paul Larson on 2013-10-21

apconfig changes to install python-gi and stop installing python-mock
and python-dateutil. Update to phablet-tools is needed for these to
work right

83. By Andy Doan on 2013-10-21

add a timeout to the master-free job

These jobs defaut to a 0 minute timeout and were getting killed.

82. By Andy Doan on 2013-10-21

don't run customizations test on sf4p

81. By Andy Doan on 2013-10-21

add maguro-03 to get-adb-id

80. By Andy Doan on 2013-10-21

make scripts/device +x permission

79. By Andy Doan on 2013-10-21

use maguro-03 for saucy testing

78. By Andy Doan on 2013-10-21

easy-locks

NOTE: these changes should all go away once we have MEGA jobs running
in production:

Joe, Paul, and myself discovered on Friday that we have a complication for our production instance now that we need to support testing saucy and trusty. Given our matrix of jobs and locking, we'd need as things currently stand to have a new set of devices dedicated so saucy.

In the long term, the MEGA jobs solve this issue. However, we need something that can limp us along for the short term. The idea here is to have our jobs use a "device lock". The master job will grab one and make sure the rest of the downstream jobs use it. This will allow you to kick off a saucy and trusty test at the same time and ensure that all of saucy runs before trusty (or vice-versa). You can also re-run an old job because each job will detect if no lock exists and will aquire one if needed.

There's one small thing missing for re-running a downstream job: we should be able to provide a parameter for the INSTALL_URL so it can validate the target has the correct image. That's less pressing than the locking logic, so I wanted to walk everyone through this patch-set first.