Merge lp:~joetalbott/cupstream2distro-config/add_autopilot_pay_ui into lp:cupstream2distro-config

Proposed by Joe Talbott on 2015-02-05
Status: Superseded
Proposed branch: lp:~joetalbott/cupstream2distro-config/add_autopilot_pay_ui
Merge into: lp:cupstream2distro-config
Diff against target: 13 lines (+2/-1)
1 file modified
stacks/head/apps.cfg (+2/-1)
To merge this branch: bzr merge lp:~joetalbott/cupstream2distro-config/add_autopilot_pay_ui
Reviewer Review Type Date Requested Status
Francis Ginther 2015-02-05 Needs Fixing on 2015-02-13
PS Jenkins bot continuous-integration Approve on 2015-02-06
Review via email: mp+248830@code.launchpad.net

This proposal has been superseded by a proposal from 2015-02-13.

Commit Message

Add autopilot tests for pay-ui.

Description of the Change

Add autopilot tests for pay-ui.

To post a comment you must log in.
1237. By Joe Talbott on 2015-02-05

add autopilot tests for pay-ui

Francis Ginther (fginther) wrote :

Adding 'generic-click-autopilot-vivid-touch' is the right job to add. This also needs an entry for:

   test_suite: pay_ui

I tried running the test job manually, but got really horrible results:
http://s-jenkins.ubuntu-ci:8080/job/generic-click-autopilot-runner-mako/760/console

The results are 'UNSTABLE' but the real problem is that the pay_ui tests can't be loaded by autopilot and therefore no tests actually run. I don't really know why these aren't working as the tests appear to be getting loaded into the proper location on the device. It looks like lp:pay-ui is missing the x-test content [1] in the click manifest file to trigger using python3.

Once test_suite gets added, this MP can be merged, but we should wait until the pay-ui tests can actually be executed.

[1] http://www.piware.de/2014/07/deb-click-schroot-lxc-qemu-phone-cloud-one-autopkgtest-to-rule-them-all/

review: Needs Fixing
1238. By Joe Talbott on 2015-02-06

pay-ui - add test_suite entry

Francis Ginther (fginther) wrote :

After a conversation with dobey, it's not possible to get the pay-ui tests to pass in their current form. They'll continue to work on it, but it might be a while before it's ready.

We'll need to keep this unmerged for a while.

Francis Ginther (fginther) wrote :

We can enable running these tests in a way that won't cause the master job to fail. This is done by adding:

  nonfatal_jobs: generic-click-autopilot-vivid-touch

instead of adding 'generic-click-autopilot-vivid-touch' to standard_jobs. This will execute the job as a child just like standard_jobs, but the results are not used by the parent job to determine pass/fail.

review: Needs Fixing

Unmerged revisions

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'stacks/head/apps.cfg'
2--- stacks/head/apps.cfg 2015-01-21 22:23:55 +0000
3+++ stacks/head/apps.cfg 2015-02-06 14:33:46 +0000
4@@ -67,7 +67,8 @@
5 daily_release: False
6 use_stack_ppa: False
7 hooks: H05set_package_version C09copy_results
8- standard_jobs: generic-click-builder-vivid-armhf
9+ standard_jobs: generic-click-builder-vivid-armhf generic-click-autopilot-vivid-touch
10+ test_suite: pay_ui
11 aggregate_tests: False
12 archive_artifacts: False
13 publish_junit: False

Subscribers

People subscribed via source and target branches

to all changes: