Activity log for bug #1338790

Date Who What changed Old value New value Message
2014-07-07 21:19:25 Nicholas Skaggs bug added bug
2014-07-07 21:19:42 Nicholas Skaggs bug task added sudoku-app
2014-07-07 21:21:01 Nicholas Skaggs bug task added ubuntu-calculator-app
2014-07-07 21:21:44 Nicholas Skaggs bug task added ubuntu-calendar-app
2014-07-07 21:22:03 Nicholas Skaggs bug task added ubuntu-filemanager-app
2014-07-07 21:22:26 Nicholas Skaggs bug task added music-app
2014-07-07 21:27:58 Nicholas Skaggs description Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE, "x-test": { "autopilot": "ubuntu_calculator_app" } For those that do, specify them like so: "x-test": { "autopilot": { "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests", "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"] } } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \ ssh -s /usr/share/autopkgtest/ssh-setup/adb
2014-07-07 21:28:52 Nicholas Skaggs bug task added reminders-app
2014-07-07 21:29:06 Nicholas Skaggs bug task added ubuntu-terminal-app
2014-07-07 21:29:20 Nicholas Skaggs bug task added ubuntu-weather-app
2014-07-07 21:29:37 Nicholas Skaggs bug task added dropping-letters
2014-07-07 21:30:49 Nicholas Skaggs description Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE, "x-test": { "autopilot": "ubuntu_calculator_app" } For those that do, specify them like so: "x-test": { "autopilot": { "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests", "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"] } } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \ ssh -s /usr/share/autopkgtest/ssh-setup/adb Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb
2014-07-07 21:34:41 Nicholas Skaggs dropping-letters: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:34:49 Nicholas Skaggs sudoku-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:02 Nicholas Skaggs ubuntu-calculator-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:05 Nicholas Skaggs ubuntu-calendar-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:08 Nicholas Skaggs ubuntu-filemanager-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:11 Nicholas Skaggs music-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:14 Nicholas Skaggs ubuntu-rssreader-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:16 Nicholas Skaggs reminders-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:18 Nicholas Skaggs ubuntu-terminal-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 21:35:22 Nicholas Skaggs ubuntu-weather-app: assignee Nicholas Skaggs (nskaggs)
2014-07-07 23:03:05 Nicholas Skaggs branch linked lp:~nskaggs/music-app/autopkg
2014-07-07 23:03:21 Nicholas Skaggs branch linked lp:~nskaggs/ubuntu-calendar-app/autopkgtest
2014-07-07 23:14:41 Nicholas Skaggs description Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtestmusic-app music_app click-buddy --dir music_app adt-run -d --shell autopkgtest/ com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb
2014-07-07 23:16:19 Nicholas Skaggs description Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtestmusic-app music_app click-buddy --dir music_app adt-run -d --shell autopkgtest/ com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtest music_app click-buddy --dir music_app adt-run -d --shell autopkgtest/ com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb
2014-07-07 23:17:12 Nicholas Skaggs description Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtest music_app click-buddy --dir music_app adt-run -d --shell autopkgtest/ com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtest music-app click-buddy --dir music-app adt-run -d --shell music-app/ music-app/com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb
2014-07-07 23:18:00 Nicholas Skaggs description Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtest music-app click-buddy --dir music-app adt-run -d --shell music-app/ music-app/com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtest music-app click-buddy --dir music-app adt-run -d --shell music-app/ com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb
2014-07-08 00:17:38 Victor Thompson music-app: status New In Progress
2014-07-08 05:41:44 Martin Pitt ubuntu-calculator-app: status New Invalid
2014-07-08 06:24:36 Martin Pitt ubuntu-calendar-app: status New Invalid
2014-07-08 07:09:19 Martin Pitt ubuntu-calendar-app: status Invalid Triaged
2014-07-08 07:28:06 Martin Pitt ubuntu-filemanager-app: status New Invalid
2014-07-08 07:35:50 Martin Pitt ubuntu-terminal-app: status New Invalid
2014-07-08 07:37:11 Martin Pitt ubuntu-calculator-app: assignee Nicholas Skaggs (nskaggs)
2014-07-08 07:37:23 Martin Pitt ubuntu-filemanager-app: assignee Nicholas Skaggs (nskaggs)
2014-07-08 07:37:33 Martin Pitt ubuntu-terminal-app: assignee Nicholas Skaggs (nskaggs)
2014-07-08 07:45:19 Martin Pitt ubuntu-weather-app: status New Invalid
2014-07-08 07:45:19 Martin Pitt ubuntu-weather-app: assignee Nicholas Skaggs (nskaggs)
2014-07-08 07:47:40 Martin Pitt bug task added ubuntu-clock-app
2014-07-08 08:02:09 Martin Pitt ubuntu-clock-app: status New Invalid
2014-07-08 08:19:50 Martin Pitt music-app: status In Progress Invalid
2014-07-08 08:19:50 Martin Pitt music-app: assignee Nicholas Skaggs (nskaggs)
2014-07-08 08:25:34 Martin Pitt bug task added gallery-app
2014-07-08 08:25:45 Martin Pitt bug task added camera-app
2014-07-08 08:26:01 Martin Pitt bug task added notes-app
2014-07-08 08:30:59 Martin Pitt dropping-letters: status New Invalid
2014-07-08 08:30:59 Martin Pitt dropping-letters: assignee Nicholas Skaggs (nskaggs)
2014-07-08 08:43:47 Martin Pitt sudoku-app: status New Invalid
2014-07-08 08:43:47 Martin Pitt sudoku-app: assignee Nicholas Skaggs (nskaggs)
2014-07-08 08:58:42 Martin Pitt ubuntu-rssreader-app: status New Invalid
2014-07-08 08:58:42 Martin Pitt ubuntu-rssreader-app: assignee Nicholas Skaggs (nskaggs)
2014-07-08 09:03:29 John Tyce bug added subscriber John Tyce
2014-07-08 09:03:34 John Tyce removed subscriber John Tyce
2014-07-08 09:03:39 John Tyce bug added subscriber John Tyce
2014-07-08 09:03:45 John Tyce removed subscriber John Tyce
2014-07-08 09:04:58 Martin Pitt reminders-app: status New Confirmed
2014-07-08 09:12:09 Martin Pitt camera-app: status New Invalid
2014-07-08 09:58:56 Martin Pitt gallery-app: status New Invalid
2014-07-08 10:30:26 Martin Pitt notes-app: status New Incomplete
2014-07-08 11:40:55 Martin Pitt ubuntu-calendar-app: status Triaged In Progress
2014-07-08 12:34:04 Martin Pitt bug added subscriber Martin Pitt
2014-07-08 15:27:03 Ubuntu Phone Apps Jenkins Bot ubuntu-calendar-app: status In Progress Fix Committed
2014-07-08 17:28:29 Nicholas Skaggs branch linked lp:~nskaggs/notes-app/ap-setup-update
2014-07-08 17:28:44 Nicholas Skaggs notes-app: status Incomplete In Progress
2014-07-08 17:28:44 Nicholas Skaggs notes-app: assignee Nicholas Skaggs (nskaggs)
2014-07-15 18:51:17 Nicholas Skaggs branch linked lp:~nskaggs/reminders-app/autopkgtest
2014-07-16 18:59:21 Nicholas Skaggs reminders-app: status Confirmed In Progress
2014-07-24 06:54:28 Ubuntu Phone Apps Jenkins Bot reminders-app: status In Progress Fix Committed
2014-08-05 12:40:01 Alan Pope 🍺🐧🐱 🦄 ubuntu-calendar-app: status Fix Committed Fix Released
2014-10-10 09:58:38 David Planella reminders-app: status Fix Committed Fix Released
2014-10-30 14:33:58 Martin Pitt description Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtest music-app click-buddy --dir music-app adt-run -d --shell music-app/ com.ubuntu.music_1.3.517_all.click --- \ssh -s /usr/share/autopkgtest/ssh-setup/adb Since autopkgtest now supports running autopilot tests for click packages, we should migrate to test provisioning and running via adt. To do this, update the manifest to specify your test dependencies (look in your debian/control at the depends specified for your *-autopilot package). Specify them like so in the manifest file (copied from http://people.debian.org/~mpitt/autopkgtest/README.click-tests.html): If a test does not need any additional dependencies, you can are all set. IE,    "x-test": {         "autopilot": "ubuntu_calculator_app"     } For those that do, specify them like so:    "x-test": {            "autopilot": {                 "command": "PYTHONPATH=tests/autopilot:$PYTHONPATH python3 -m autopilot.run run foo_tests",             "depends": ["ubuntu-ui-toolkit-autopilot", "autopilot-touch"]              }    } Tests can then be run by calling them via adt and specifying a target, like a phone. EG, adt-run folder-of-branch/ click-package.click --- \ test-runner For example; adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- \       ssh -s /usr/share/autopkgtest/ssh-setup/adb Note you'll need to provide the click package, so build it first. If you have native code, you'll need to cross compile. You can use click-buddy or qtcreator (or your favorite tool) to build. ----------- Example; bzr branch lp:~nskaggs/music-app/autopkgtest music-app click-buddy --dir music-app adt-run music-app/ com.ubuntu.music_1.3.517_all.click --- ssh -s adb
2014-11-24 17:31:04 Launchpad Janitor branch linked lp:~ubuntu-branches/ubuntu/vivid/reminders-app/vivid-proposed
2014-11-24 18:05:51 Launchpad Janitor reminders-app (Ubuntu): status New Fix Released
2015-01-13 19:35:37 Nicholas Skaggs notes-app: status In Progress Invalid
2015-01-13 19:35:37 Nicholas Skaggs notes-app: assignee Nicholas Skaggs (nskaggs)