[01:02] <balloons> smartboyhw_, howdy
[01:03] <smartboyhw_> balloons, howdy I got a unexpected holiday today
[01:04] <smartboyhw_> (smartboyhw) Hi madeinkobaia, I got a surprise holiday today, a Black Rainstorm Warning and all students are banned for school
[01:04] <smartboyhw_> balloons: ^ the reason
[01:13] <balloons> smartboyhw_, black rainstorm?
[01:13] <balloons> nice.. stay safe
[01:14] <balloons> http://www.scmp.com/news/hong-kong/article/1243223/black-rainstorm-warning-issued-heavy-rain-pummels-hong-kong
[01:16] <smartboyhw_> balloons: Yep. But you read SCMP?!
[01:18] <balloons> smartboyhw_, no if anything I'll read Asia Times
[01:18] <balloons> hurricane season is starting for us here as well
[01:20] <smartboyhw_> balloons: Torpedo?
[01:20] <smartboyhw_> Seems like it killed a lot of people:(
[01:29] <balloons> Tornado you mean?
[03:40] <pitti> Good morning
[03:45] <SergioMeneses> pitti, evening here
[03:45] <SergioMeneses> :)
[03:46] <pitti> hey SergioMeneses
[03:46] <SergioMeneses> pitti, how's everything?
[03:48] <pitti> quite fine, thanks! how about you?
[03:49] <SergioMeneses> pitti, tired... today was my first day in a new job
[03:51] <pitti> oh, congratulations
[03:51] <SergioMeneses> pitti, thanks
[06:30] <Noskcaj> smartboyhw__, Testdrive: i've contacted dustin, but he has no time yet.
[06:33] <Noskcaj> smartboyhw__, have you put any more time into getting ubuntu gnome in? if not, i'll have a look. do you think there would be any differences other than swapping from "kylin" to "gnome" in the diff?
[06:48] <jibel> good morning
[06:52] <smartboyhw__> Noskcaj: Shouldn't be...
[06:52] <smartboyhw__> Just the same thing
[06:52] <pitti> bonjour jibel
[06:58] <jibel> bonjour pitti
[08:52] <chappers> morning all
[08:54] <Noskcaj> evening chappers
[10:19]  * pitti looks at the apport adt failure
[10:19] <pitti> ileNotFoundError: [Errno 2] No such file or directory: '/etc/motd'
[10:19] <pitti> wow, we really stripped down these VMs
[12:40] <pitti> jibel: seems udisks2 adt failed again because scsi_debug is not available; it does work locally (well, there's one test case failure which I'll fix now)
[12:40] <pitti> jibel: do you know why the jenkins VM doesn't have linux-extra, but my prepare-testbed VM does?
[12:41] <jibel> pitti, no, this is something that had been a while ago especially for this case, I'll have a look.
[12:42] <pitti> jibel: I thought we'd use the very same script for building the jenkins VM, don't we?
[12:47] <jibel> pitti, we install linux-image-generic which depends on linux-image-extra-3.9.0-2-generic
[12:47] <pitti> hm, strange
[12:48] <jibel> and I confirm scsi_debug.ko is in linux-image-extra-3.9.0-2-generic
[12:48] <pitti> ERROR: could not insert 'scsi_debug': Cannot allocate memory
[12:49] <pitti> hm, so maybe it's too small then
[12:50] <pitti> oh, amd64 indeed doesn't have that issue, just i386
[12:50] <jibel> pitti, ah, is it a problem with vmalloc too small ?
[12:51] <jibel> it is set to 384MB on i386
[12:51] <pitti> jibel: it tries to allocate a 300 MB scsi_debug disk
[12:52] <jibel> pitti, okay, I'll increase vmalloc to 500MB see if it fixes the problem
[12:53] <pitti> jibel: merci
[12:53] <pitti> jibel: I'll do another upload soon
[13:13] <jibel> pitti, fixed in r181 and published in the lab. We'll need to reprovision the VMs, do you want them now or wait the next automated builds tomorrow morning?
[13:13] <pitti> jibel: tomorrow is fine
[13:13] <pitti> jibel: merci beaucoup!
[13:13] <jibel> there is not a lot of activity ATM, reprovisioning before your upload will not hurt anyone
[13:14] <pitti> jibel: if it takes you less than 10 s (i. e. just a button click), sure; but I don't want to pile even more work on you
[13:15] <pitti> ok, fixed both udisks test failures upstream now
[13:15] <jibel> builds are running
[13:15] <pitti> cheers!
[15:12] <pitti> jibel: hm, I can't run lxc-ls --fancy; how can I get to the jhbuild lxc on rabisu now? <IP_ADDRESS> doesn't work any more
[15:14] <pitti> jibel: ah, I can do that as user ubuntu, nevemrind
[17:06] <Vasudevan> Archive Manager (file-roller) - basic manual interaction - create a new archive 'test.tar.gz' or 'test.zip', add couple of files;  throws error msg -  'error opening file'; how to work around this?
[17:11] <balloons> Vasudevan, is this an autopilot test or a manual test?
[17:11] <DanChapman> When writing autopilot tests, are we to do it in saucy or raring?
[17:11] <Vasudevan> auto pilot script failed, so was trying it out manually
[17:17] <balloons> Vasudevan, ahh.. That sounds like a bug, but I'm happy to try it right now and reproduce :-)
[17:18] <balloons> DanChapman, we can do it in raring or saucy. However, the target for where they will be run is always the development version of ubuntu, which is currently saucy
[17:18] <Vasudevan> balloons, my dev box is still quantal 12.10 ...
[17:18] <balloons> Vasudevan, yes, and you had to do some workarounds to get autopilot 1.3 working right?
[17:19] <balloons> Vasudevan, so let me try repeating your steps right now
[17:19] <DanChapman> balloons, thanks :D
[17:19] <Vasudevan> yes - to build autopilot 1.3 on quantal I had to disable lttng (ext) modules..
[17:19] <balloons> Vasudevan, ok, so I added files just fine.. I'm running saucy
[17:20] <balloons> is it just the file your adding?
[17:22] <Vasudevan> balloons,  no - i tried adding and extracting and get error msg from the file-roller app on 12.10
[17:23] <Vasudevan> also saw couple of file-roller:8385 gtk-CRITICAL msgs on the console..
[17:29] <balloons> Vasudevan, bizarre.. hmm
[17:29] <balloons> do I have a quantal install lying around
[17:30] <balloons> it seems I do.. let me boot it
[17:33] <Vasudevan> balloons, this is the msg - (file-roller:8385): Gtk-CRITICAL gtk_device_grab_add: assertion 'GDK_IS_DEVICE (device)' failed
[17:37] <balloons> Vasudevan, hmm.. so it's not file-roller specific then is my guess
[17:38] <balloons> is quantal up to date?
[17:38] <Vasudevan> I think not..
[17:39] <balloons> works fine for me..
[17:39] <balloons> on quantal :-0
[17:44] <Vasudevan> ok, will try running updates - is there a log file that I can look for these types of apps - does logging need to enabled in a conf file?
[17:48] <balloons> log file for file-roller?
[17:48] <balloons> you can log autopilot testcase runs (as you can imagine).. you can even record them
[17:48] <balloons> anyways, if it's still an issue after updating you definitely have a bug..
[17:53] <Vasudevan> balloons, yes - debug events and msgs from file-roller and other default apps that we test - tried to tail var/log/lightdm and was wondering if there other specific logs that we could look at
[17:54] <Vasudevan> let me update and try again, thanks again.
[17:55] <balloons> Vasudevan, each app is different in logging.. for general system level logs /var/log is your friend
[17:55] <balloons> https://help.ubuntu.com/community/LinuxLogFiles
[17:55] <balloons> sometimes apps will have verbose or debugging mode
[17:55] <balloons> I don't know if file-roller has such a thing
[17:56] <Vasudevan> ok, thanks
[17:56] <balloons> file-roller --help-all has some debug setting abilities
[18:01] <Vasudevan> balloons, thanks.
[19:03] <DanChapman> i'm having trouble running 'autopilot launch' here is the output i'm getting http://paste.ubuntu.com/5691358/
[19:04] <DanChapman> autopilot vis works fine. But trying to have a look at the introspection tree for gedit. Any ideas anyone?
[19:08] <DanChapman> ahh just found bug report https://bugs.launchpad.net/autopilot/+bug/1169593
[19:19] <balloons> DanChapman, yes, some apps can give trouble
[19:19] <balloons> however gedit is not among them
[19:19] <balloons> it should work :-)
[19:20] <balloons> what version of autopilot do you have?
[19:20] <DanChapman> balloons its not for me even trying to pass -i
[19:20] <balloons> apt-cache show python-autopilot
[19:21] <balloons> autopilot launch gedit
[19:21] <balloons> Autopilot GTK interface loaded.
[19:21] <balloons> should get that :-)
[19:21] <DanChapman> version: 1.2daily13.04.09-0ubuntu1
[19:21] <balloons> hmm.. ok that's fine
[19:21] <balloons> are you missing the introspection library
[19:22] <DanChapman> whats the lib name?
[19:24] <balloons> libautopilot-gtk and libautopilot-qt respectively
[19:24] <balloons> at one point they were installed by default when installing python-autopilot, but I don't believe that's an issue anymore
[19:26] <DanChapman> Ahh that got it, libs were not there.
[19:27] <DanChapman> thanks balloons
[19:28] <balloons> DanChapman, ahh.. ok, so that packaging fix must be in the new version of autopilot, 1.3
[19:30] <balloons> DanChapman, found it :-) https://bugs.launchpad.net/autopilot/+bug/1158983
[19:30] <elfy> balloons: do you happen to have an easily digested starting point to working with testcases?
[19:31] <balloons> elfy, watch the video on youtube would be my recommendaion
[19:31] <balloons> http://www.youtube.com/watch?v=VO7DdlUSt_4&feature=youtu.be
[19:31] <elfy> mmm - I'm not good with doing that, lose concentration easily - nothing to read?
[19:32] <balloons> elfy, https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual
[19:32] <elfy> ta - got as far as getting them with bzr this morning
[19:32] <balloons> you get the words or the video, your choice.. the video is more in-depth , more visual, etc
[19:32] <elfy> k - if necessary I'll go to youtube
[19:33] <balloons> also this is good to make sure your setup right: https://wiki.ubuntu.com/QATeam/ContributingTestcases/Launchpad
[19:33] <balloons> it's all in the tutorial tho
[19:33] <elfy> k
[19:43] <elfy> balloons: all looks 'fairly' self-explanatory - I'm sure there'll be need for some xubuntu ones - especially if we do this new package tracking
[19:44] <balloons> elfy, yes, there is a need for xubuntu specific tests. Up until now that has been tossed into the image folder and done as part of the image testing
[19:44] <elfy> yep
[19:44]  * elfy sees busy in his future :p
[20:27] <Letozaf> balloons, Hi
[20:28] <balloons> Letozaf, hello :-)
[20:28] <Letozaf> balloons, howzit ?
[20:29] <Letozaf> balloons, I was looking at autopilot 1.3 for porting 1.2 tests
[20:29] <balloons> indeed
[20:29] <Letozaf> balloons, I was trying out the gedit test
[20:29] <Letozaf> balloons, first looking at what you did with the firefox one
[20:30] <Letozaf> balloons, but I do not understand why  self.assertThat(btn, NotEquals(None)) gives an error MismatchError: None == None
[20:32] <Letozaf> balloons, or is it better we see this tomorrow during the hackaton
[20:33] <balloons> Letozaf, hmm..
[20:33] <balloons> we can talk about it now :-)
[20:34] <Letozaf> balloons, it's the test_save_and_open_a_file
[20:35] <Letozaf> balloons, where you click on the new "button"
[20:35] <balloons> rightm sure
[20:35] <Letozaf> balloons, in autopilot 1.2 it used to work, is this different in 1.3 ?
[20:36] <balloons> I feel like it's just a python erorr Letozaf
[20:36] <balloons> I'm trying to think about it.. it might be better to look at the code
[20:36] <Letozaf> balloons, the weired thing is that it's the same exact code as in autopilot 1.2 and there it used to work
[20:36] <Letozaf> balloons, I am using Saucy and autopilot 1.3
[20:38] <thomi> Letozaf: might be a good idea to open vis and make sure you'er selecting on the right properties
[20:38] <balloons> ohh.. good point
[20:38] <balloons> I need to grab 1.3 on this pc
[20:38] <thomi> select_single & select_many changes how they work slightly between 1.2 and 1.3
[20:39] <Letozaf> thomi, but do you think things have changed respect to autopilot 1.2 ? I mean that same property used to work
[20:39] <Letozaf> thomi, and now not anymore, the error though is the one when the property is wrong
[20:40] <Letozaf> thomi, so maybe you are right, it's just weired that it was ok with 1.2
[20:40] <balloons> Letozaf, ohh.. are you running the non-introspection version of gedit
[20:40] <balloons> man, so much housekeeping to do tomorrow :-)
[20:41] <thomi> Letozaf: maybe pastebin your failing test, and I can take a peek?
[20:41] <balloons> Letozaf, your looking at this right?         btn = self.app.select_single('GtkToolButton', label='_New')
[20:41] <balloons>         self.assertThat(btn, NotEquals(None))
[20:41] <balloons>         self.mouse.move_to_object(btn)
[20:42] <Letozaf> http://paste.ubuntu.com/5691654/
[20:43] <Letozaf> thomi, #open a new blank document
[20:43] <Letozaf> btn = self.app.select_single('GtkToolButton', label='_New')
[20:43] <Letozaf> self.assertThat(btn, NotEquals(None))
[20:44] <Letozaf> balloons, yes
[20:44] <Letozaf> balloons, right lines
[20:49] <Letozaf> thomi, balloons in vis I can find that property, it's still there
[20:50] <thomi> Letozaf: ahhh, sorry - I was being dumb. This is a known bug, and there's actually already a patch to fix it, I just need to review it
[20:50] <thomi> Letozaf: it's a problem with autopilot-gtk
[20:51] <Letozaf> thomi, ok fine
[20:51] <Letozaf> thomi, so I will wait :D thanks
[20:52] <thomi> Letozaf: well, if you felt like it, you could grab the branch that's supposed to fix the issue, build it, install it, and tell us if it fixes the issue for you or not
[20:53] <Letozaf> thomi, ok, I will try, but tomorrow evening, it's late here in Italy now, better go to bed, but tomorrow I will do it :D
[20:54] <thomi> Letozaf: ok, it might be merged by then, so check the commit log in lp:autopilot-gtk first :)
[20:54] <Letozaf> thomi, oh! sure! sorry but tomorrow got to get up early :(
[20:54] <Letozaf> thomi, anyway I will let you know
[20:55] <Letozaf> thomi, balloons 'night guys
[20:55] <thomi> no worries
[20:55] <thomi> 'night
[20:55] <balloons> bah.. she's gone :-) thomi ok, I'll probably give it a whirl tomorrow during the fest
[21:03] <phillw> balloons: what sort of feed back did you get from your classroom session? It looks like at least one new tester has come forward (and I got a lubuntu new comer). Well worth an hour of time if we can get a new tester each session :D
[21:07] <balloons> phillw, glad to hear it
[21:07] <balloons> yes there's been some folks stirring up at the start of the cycle which is great to see :-)
[21:08] <balloons> chilicuil, quite the storm of new bugs your filing :-) I didn't expect so many
[21:12] <chilicuil> balloons: those are the default applications just for edubuntu, expect a little bit more from lubuntu, xubuntu, kubuntu, mythbuntu and ubuntu studio =)
[21:12] <balloons> chilicuil, that many really?
[21:13] <balloons> do we think it would be helpful to tag them in any way? I was expecting say 10-20 apps for each flavor
[21:13] <chilicuil> balloons: yep, edubuntu, mythubuntu and ubuntu studio release dvd size distributions
[21:13] <balloons> a default file manager, browser, music player, video player, office suite
[21:13] <balloons> chilicuil, ohh right.. my goodness
[21:14] <chilicuil> balloons: if you want I can tag them
[21:14] <chilicuil> currently, I'm only adding the 'todo' tag
[21:14] <balloons> yea, I think making it easy to show what belong to what flavor(s) would be good
[21:15] <balloons> especially since there is so many :-) So for lubuntu we'll have a bit saner number right?
[21:15] <chilicuil> it sounds reasonable, yep, for lubuntu there will be less, also some applications are used in more than one flavor, so they should be less
[21:16] <phillw> balloons: we did discuss, last cycle, about creating a spread sheet (table) to list applications and what flavours use them, maybe now is a good time to make a start on it?
[21:18] <phillw> e.g. lubuntu uses the xcfe power-manager so any test of that as an application would be applicable to both lubuntu and xubuntu (possibly studio) etc.
[21:18] <balloons> phillw, what would be the purposed of the list? information or ?
[21:20] <phillw> balloons: it would allow application tests cases to be monitored accross the flavours. e.g. if a there is a test case for xcfe power-manager, either a lubuntu or xubuntu tester could run that test case and the result would be applicable to both flavours?
[21:21] <balloons> phillw, I'm not sure we can paint with such broad strokes
[21:21] <balloons> it would be up to the teams if that was true or not.. That said, if that was the purpose of the list, I think it's better managed inside the tool than a list
[21:22] <balloons> that said, sharing tests and potentially results is a good thing.. and something we want :-)
[21:22] <phillw> balloons: do not forget writing them :D
[21:26] <phillw> balloons: a classic case of a bug affecting all flavours is one where a browser (chromium / fire fox) has an issue that one tester picks up, but others have not noticed :)
[21:27] <phillw> s/all/multiple
[21:34] <balloons> phillw, certainly any non-distro specific issue is useful :-)
[21:36] <phillw> balloons: at present I get *all* chromium bugs (but that is via lp), I'm just wondering if the apps qa-tracker will alert another a flavour of a bug found on an application that they both use?
[21:39] <chilicuil> that's currently not possible, AFAIK, and it's related to the discussion we had about enlighten some bugs in the qa tracker even if those bugs wasn't found particulary by following the testcases
[21:41] <phillw> chilicuil: okies, thanks :)
[21:41] <balloons> indeed.. I think chilicuil is right here
[21:41] <balloons> we talked about filtering important stuff or showing tracker bugs, etc, etc
[21:41] <balloons> Requires work on the tracker, but it is possible as long as we define what we want
[21:44] <phillw> I would imagine so, but there must be an API on lp that allows me to receive (in this example)
[21:44] <phillw> You received this bug notification because you are a member of Lubuntu
[21:44] <phillw> Packages Team, which is subscribed to chromium-browser in Ubuntu.
[21:53] <phillw> and, not really related. the bug is asking ubuntu to "stop messing about" and move from v25 to v27 which has a lot of CVE's fixed (security issues)
[21:54] <phillw> the stable is actually newer than my development one!


[00:44] <minasota> Ok, so if you all aren't in this channel, where else are y'all camping out?
[00:45] <minasota> where is everyone?
[00:59]  * wrst thinks it is a bit cold for camping
[01:32] <Unit193> I'm in here, technically.
[01:34] <wrst> Me too Unit193 we are always here
[01:36] <Unit193> wrst: I wasn't for a minute or so this afternoon!
[01:37] <wrst> What happened?
[01:37] <Unit193> Eh, router issues again, no big.
[01:42] <wrst> Ahh
[02:00] <cyberanger> minasota: Trucking, so I'm not on much
[02:43] <Unit193> I'm also in about 50+ channels in this Irssi session.
[03:29] <wrst> Ouch


[01:45] <Kireji> I'd like to buy/create an ubuntu laptop with a fairly recent chipset and a design like the single-frame titanium macbook pro
[01:46] <Kireji> are there any ubuntu compatible hardware that might be close to that where I can start researching?
[11:38] <Daviey> Hola... So.. if i want to add a test to the upgrade tester, what do i need to do?
[11:38] <Daviey> gema / jibel ?
[11:39] <gema> Daviey: ?
[11:39] <Daviey> gema: ^^ above
[11:39] <gema> yes I am thinking
[11:40] <gema> to which job do you want to add a test?
[11:40] <Daviey> gema: bug 923685 looks like a good candidate for post upgrade inspection
[11:40] <ubot4`> Launchpad bug 923685 in resolvconf (Ubuntu) "New resolver package overwrites manually created resolv.conf on server (affects: 1) (heat: 6)" [High,New] https://launchpad.net/bugs/923685
[11:40] <jibel> Daviey, Hello
[11:40] <Daviey> hello jibel, having fun? :)
[11:42] <gema> Daviey: ideally if you write a pyunit script for the test case, we should be able to create a job for it
[11:42] <gema> for the time being
[11:42] <gema> am I right, jibel ?
[11:42] <jibel> Daviey, file a bug against update-manager (this is where auto-upgrade-tester is), write your requirements, the test case and attach a test script ideally a python unittest
[11:42] <jibel> Daviey, and assign the report to the QA team
[11:43] <jibel> and I've fun, yes I do.
[11:43] <Daviey> jibel: Do you have a good example of your unittest style?
[11:44]  * Daviey is seriously stoked we have unit testing framework now btw. :)
[11:44] <jibel> Daviey, http://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/view/head:/AutoUpgradeTester/post_upgrade_tests/test_lts_upgrade_user.py
[11:44] <jibel> Daviey, this is an example of what pitti write for the desktop team
[11:45] <Daviey> jibel: So, does this get run in it's own sterile enviroment - or along with other tests?
[11:45] <jibel> Daviey, depends on your requirements.
[11:46] <Daviey> jibel: how does that get declared?
[11:47] <jibel> it can be run in it's own environment, in this case we'll create a specific profile, or with other test, in which case, we'll add the test to an existing profile
[11:47] <gema> Daviey: ideally , unless the test is destructive , you are better off running it with others
[11:48] <gema> Daviey: more realistic environment
[11:48] <Daviey> jibel: So, if i land a file into that location, it doesn't get picked up on it's own - you fiddle with jenkins?
[11:48] <Daviey> gema: right.. just trying to understand the infrastucture.
[11:48] <gema> Daviey: the infrastructure is not there yet
[11:48] <gema> it 's all manual at the moment
[11:48] <jibel> Daviey, by default everything in post_upgrade_test is run
[11:49] <jibel> I manually configure the profiles to blacklist specific tests
[11:49] <gema> we won't be able to pick things automatically (not that we would, because we like to review stuff) until next cycle
[11:49] <Daviey> gema: okay, how do i invoke the tester for local test development?
[11:49] <Daviey> jibel: ah!
[11:49] <jibel> for example it doesn't make sense to run desktop test on server upgrades
[11:49] <jibel> or lts test on oneiric to precise upgrades
[11:49] <Daviey> right
[11:50] <Daviey> jibel: well, seemed pitti coded logic to drop out if it's mot LTS->LTS
[11:50] <jibel> Daviey, https://wiki.ubuntu.com/QATeam/UpgradeTestingSetup
[11:51] <jibel> Daviey, yup, I added that logic, don't bother with that now. write the test, describe the test environment and conditions required to run the test, and we'll figure how to fit it in.
[11:52]  * jibel -> lunch. back in 45mn
[11:54] <Daviey> thanks jibel & gema
[12:28] <jamespage> jibel: are we using lxc in the main QA lab?
[12:46] <jibel> jamespage, I used it in the lab to setup an environment for litmus and for package testing.
[12:46] <jamespage> jibel: ack - I'm just looking at the work m_3 has done to automatically test charms - it uses the lxc local provider for juju
[12:47] <jamespage> linking about where to deploy longer term...
[16:03] <roadmr> balloons: hey! an Ubuntu Friendly meeting is starting in #ubuntu-meeting, in case you're interested
[16:04] <roadmr> balloons: I think the topics today are mainly technical, still I thought I'd give you a heads-up
[16:11] <balloons> roadmr, on ,y wat thanks
[23:54] <petko> hey guys , I want to ask if there's any way of using the update manager to get alpha 1 or the daily builds or must I go through the USB/CD install ?