Merge lp://qastaging/~canonical-platform-qa/ubuntu-power-tests/preserve-powerd-cli into lp://qastaging/ubuntu-power-tests

Have we made communications or filed a bug so that we may get this fixed in trunk for autopkgtest? I would rather not carry another forked adb script that doesn't keep up to date.

I think it's ok to use it in the interim, as long as we have a bug and intentions to have it fixed upstream. (the hard part is keeping pressure on this and actually following it up and getting it updated.

One inline comment

Thanks Chris, I've already asked Martin about this and filed a bug [1], also mentioned in the forked file.

[1] https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1441023

Comment inline about not losing task to keep test metadata for which tests should have screen on. Other than that, LGTM.

Ok, I've reverted the README TODO comment to keep an eye on how to designate which test should keep the screen on, right now the only thing that comes to my mind is identifying the tests by name and that seems to be a bit brittle.

Cheers!

> Ok, I've reverted the README TODO comment to keep an eye on how to designate
> which test should keep the screen on, right now the only thing that comes to
> my mind is identifying the tests by name and that seems to be a bit brittle.

Yeah, I want a better solution than that, but I don't have one yet. We can discuss it with the team.

>
> Cheers!

FAILED: Autolanding.
No commit message was specified in the merge proposal. Hit 'Add commit message' on the merge proposal web page or follow the link below. You can approve the merge proposal yourself to rerun.
https://code.launchpad.net/~canonical-platform-qa/ubuntu-power-tests/preserve-powerd-cli/+merge/255252/+edit-commit-message

FAILED: Continuous integration, rev:9
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https://code.launchpad.net/~canonical-platform-qa/ubuntu-power-tests/preserve-powerd-cli/+merge/255252/+edit-commit-message

http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-ci/2/
Executed test runs:
    FAILURE: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-amd64-ci/2/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-armhf-ci/2/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-i386-ci/2/console

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-power-tests-ci/2/rebuild

FAILED: Continuous integration, rev:9
http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-ci/3/
Executed test runs:
    FAILURE: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-amd64-ci/3/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-armhf-ci/3/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-i386-ci/3/console

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-power-tests-ci/3/rebuild

For the record, bug 1441023 is fixed in git now. CI has a LP recipe to build packages from autopkgtest git and use that in production; if you need that in vivid proper, please let me know.

PASSED: Continuous integration, rev:10
http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-ci/4/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-amd64-ci/4
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-armhf-ci/4
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-i386-ci/4

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-power-tests-ci/4/rebuild

> For the record, bug 1441023 is fixed in git now. CI has a LP recipe to build
> packages from autopkgtest git and use that in production; if you need that in
> vivid proper, please let me know.

Thanks a lot pitti for this immediate fix! :) The fork works for this sprint but we should allocate time to remove it as soon as possible.

Updated to use the --keep-screen-active option

PASSED: Continuous integration, rev:11
http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-ci/5/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-amd64-ci/5
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-armhf-ci/5
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-i386-ci/5

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-power-tests-ci/5/rebuild

We're handling this a different way now. I think we should document the DISPLAYON variable, among others, in a separate proposal. I filed a bug for that here:
https://bugs.launchpad.net/ubuntu-power-tests/+bug/1455096
We can get it made into a card at some point.