[01:52] <ePierre> hi everyone!
[06:18] <pitti> Good morning
[08:57] <ePierre> hi guys
[08:57] <ePierre> what is the difference between checkbox and autopilot?
[08:57] <ePierre> https://launchpad.net/checkbox
[08:59] <Noskcaj> ePierre, Autopilot is automated testing, checkbox is an old tool for seeing if hardware works on ubuuntu
[09:03] <jibel> development of checkbox might have started several years ago, it is still actively maintained and used.
[09:04] <Noskcaj> jibel, old meaning it's been around for ages, i should have worded that better
[09:04] <jibel> it's a rather generic test runner not only for hardware
[09:06] <jibel> while autopilot is specialized on GUI testing. You could for example run autopilot tests with checkbox
[09:08] <ePierre> oh ok
[09:09] <ePierre> is there any online examples of what can checkbox do?
[09:09] <ePierre> cause with autopilot, you write tests the way you would write unit tests
[09:09] <ePierre> but with checkbox I'm not so sure... I've seen the wiki page, but it's very generic and doesn't enter too much into details
[09:24] <jibel> ePierre, I don't know about online documentation but lp:checkox probably contains all the information you need
[09:32] <brendand> ePierre, the main things that checkbox offers are the ability to gather hardware information, and the ability to run manual tests alongside automated tests
[09:33] <brendand> ePierre, http://plainbox.readthedocs.org/en/latest/ is probably the best documentation, but it is still very technical
[09:35] <brendand> ePierre, what are you planning on testing?
[09:36] <ePierre> brendand, thanks for this! so PlainBox is a rewrite of checkbox...
[09:36] <ePierre> I was just curious, this morning I was discussing with someone from Canonical who mentioned this tool, so I was having a look and was wondering the details compared to autopilot, which is also dev by Canonical
[09:37] <brendand> ePierre, we still call it checkbox, but it's built on top of plainbox now
[09:39] <ePierre> oh ok
[09:39] <ePierre> so plainbox is more like the guts of checkbox :)
[10:05] <pitti> balloons: so, two improvements in autopkgtest git head:
[10:05] <pitti> balloons: you can now run adt-run under ADT_AUTOPILOT_MODULE=ubuntu_calculator_app.tests.test_simple_page.TestSimplePage.test_divide_priority i. e. overwrite the "autopilot_module" value
[10:05] <pitti> balloons: but *shht*, this is an utter hack for now and should be cleaned up
[10:05] <pitti> balloons: and it doesn't download python2 dependencies any more, as they are useless anyway
[10:06] <pitti> balloons: and I chopped off one minute from the workaroud for bug 1337253
[10:47] <njin> Hi, have we got a chan for unity8 ?
[10:48] <njin> Is apport deprecated in favor of whoopsie in unity8 ?
[10:48] <pitti> njin: no, the two work together
[10:48] <pitti> apport intercepts crashes and creates reports, whoopsie uploads them to errors.ubuntu.com
[10:49] <njin> hi pitty, in unity8 if I run ubuntu-bug it reply to use whoopsie-upload-all
[10:49] <njin> pitti:^^
[10:50] <pitti> njin: what are you trying to do? upload an existing .crash or report a bug?
[10:50] <pitti> reporting a bug should just work normally, and whoopsie isn't involved there
[10:50] <njin> just trying to report a bug with a feaure request
[10:51] <pitti> so, "ubuntu-bug packagename"?
[10:51] <njin> ubuntu-bug unity-control-center...reply to use whoopsie-upload-all
[10:52] <njin> but is the same with ubuntu-bug linux too
[10:52] <pitti> ubuntu-bug linux works fine on current phone
[10:52] <pitti> unity-control-center isn't installed
[10:52] <pitti> (and it works on current Ubuntu desktop)
[10:52] <pitti> so what is "unity 8" in your context/
[10:52] <pitti> ?
[10:53] <njin> ok, reboot the unity8 of today and retest, at least can i ping you ?
[10:53] <pitti> njin: it would be helpful if you could put your precise command and the result into a pastebin
[10:54] <njin> ok I will try
[10:59] <jibel> pitti, I noticed what njin said on the phone but not on other environment
[10:59] <jibel> $ ubuntu-bug unity8
[10:59] <jibel> usage: whoopsie-upload-all [-h] [-t TIMEOUT]
[10:59] <pitti> phablet@ubuntu-phablet:~$ ubuntu-bug unity8
[11:00] <pitti> *** Collecting problem information
[11:00] <pitti> jibel: *confused*
[11:00] <jibel> ah
[11:00] <pitti> what does one have to do with the other?
[11:00] <jibel> popey also had this problem
[11:03] <jibel> pitti, touch /var/lib/apport/autoreport
[11:03] <jibel> then ubuntu-bug <package>
[11:08] <pitti> ah, indeed
[11:08] <pitti> this makes no sense
[11:09] <pitti> this should only be used when uploading crash reports, not bugs
[11:09] <pitti> bug report appreciated
[11:10] <pitti> jibel: thanks for pointing out!
[11:12] <jibel> pitti, yw, thanks to njin for raising the issue
[11:15] <jibel> pitti, bug 1339663 , feel free to re-title
[11:15] <pitti> thanks
[12:31] <rhuddie> fginther, I wonder if you can help me work out why I never get any Jenkins results added to any of my MPs? e.g. https://code.launchpad.net/~rhuddie/gallery-app/add-photos-page-object/+merge/225962
[14:16] <balloons> rhuddie, likely you don't get jenkins as you are not part of the dev team
[14:17] <rhuddie> balloons, ah ok. I thought it would be something like user groups
[14:18] <balloons> rhuddie, not sure how your collegues have solved it. we have a meta group for the community core apps for instance
[14:19] <balloons> pitti, the improvements sound nice. I'll give it a run and see what kind of speed we get now
[14:19] <pitti> hey balloons
[14:19] <pitti> balloons: vila set up an automatic recipe, if you care for a deb more than running out of git: https://code.launchpad.net/~vila/+recipe/autopkgtest-test-vila
[14:20] <rhuddie> balloons, I was thinking Canonical Platform QA Team would do similar, but seems not
[14:20] <balloons> pitti, oO.. yep, grabbing the deb
[15:31] <fginther> rhuddie, the jenkins that runs test for those MPs uses a user based whitelist. I've added you so you should start to see test results.
[15:32] <rhuddie> fginther, thanks a lot :)
[16:01] <rvr> elopio: I remember that you were working with faked online accounts, right?
[16:04] <elopio> rvr: real online accounts through the command line.
[16:05] <rvr> elopio: Haven't use it... is that tool able to create a faked facebook account?
[16:06] <elopio> rvr: yes. Take a look at account-console
[16:06] <elopio> rvr: and http://bazaar.launchpad.net/~reminders-app-dev/reminders-app/trunk/view/head:/tests/autopilot/reminders/credentials.py
[16:07] <rvr> elopio: Oh, great, thanks
[17:22] <jibel> bdmurray, for oops on errors.ubuntu.com there is a field called 'SystemIdentifier', do you know what it is for a phone?
[17:22] <jibel> because for several reported uploaded from the same device it is not always the same
[17:23] <jibel> for example: https://errors.ubuntu.com/oops/1d60e754-0763-11e4-8972-fa163e339c81
[17:23] <jibel> and https://errors.ubuntu.com/oops/4a7f8b7c-0741-11e4-8c80-fa163e4ccdf2
[17:23] <jibel> bdmurray, I got the list of oops on my phone with: awk '/OOPS/ {print "http://errors.ubuntu.com/oops/"$9}' /var/log/syslog
[17:25] <bdmurray> jibel: I believe its the first network interface that is available and there is a plan to cache the SystemIdentifier on disk after the first time it is created to prevent this from happening
[17:27] <jibel> bdmurray, ok, so the order can change and the id too. thanks. Do you have a recipe to build it like <some command>|sha512sum ? so I can find all the reports for a given device?
[17:29] <jibel> i've been enable to match any of the systemidentifier on errors.u.c with what I tried
[17:29] <jibel> *unable
[17:30] <bdmurray> jibel: I'm looking for the gdbus command to look it up
[17:30] <bdmurray> gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.GetIdentifier
[17:32] <bdmurray> jibel: did that work for you?
[17:33] <jibel> bdmurray, perfect, but it returns yet another identifier :)
[17:34] <jibel> and nothing on errors for this id
[17:35] <jibel> bdmurray, do you know when the change to cache the SystemIdentifier will happen?
[17:35] <bdmurray> jibel: is this whoopsie version 0.2.34? there was a recent change that might have been bad
[17:37] <jibel> bdmurray, it is 0.2.34. On mako build #122
[17:38] <bdmurray> jibel: okay, I'll have a look
[17:39] <jibel> bdmurray, thank you
[17:57] <elopio> om26er: you wrote the system settings tests for the about page, right?
[17:57] <om26er> elopio, yes I did a while ago
[17:58] <elopio> I need your help. This is driving me nuts.
[17:58] <elopio> https://code.launchpad.net/~elopio/ubuntu-system-settings/refactor_about_tests/+merge/225425
[17:58] <elopio> the tests are failing on the only part of the code that I didn't touch.
[18:08] <om26er> elopio, otto sucks, that problem is in otto, it goes away sometimes and gets back the others
[18:09] <elopio> om26er: my branch has never succeeded.
[18:09] <elopio> I'll rebuild.
[18:09] <elopio> have you reported the bug?
[18:09] <om26er> elopio, It just went away the last time I was asked to work on it
[18:10] <om26er> i.e. I started investigating but was later told by the developer it is working now, probably due to re-deployment of otto.
[18:11] <elopio> om26er: and now the one with system settings is brendan, right?
[18:11] <om26er> elopio, I believe so