[08:06] <rickspencer3> jibel, good morning
[08:06] <jibel> rickspencer3, good morning
[08:07] <rickspencer3> jibel, hope things are well
[08:07] <rickspencer3> I noticed that the daily smoke tests don't seem to be running?
[08:08] <jibel> rickspencer3, well, that's what I'm looking. everything looks right, images are available but tests didn't start.
[08:08] <rickspencer3> k
[08:09] <jibel> jamespage, ping
[08:23] <jibel> rickspencer3, a restart fixed the problem and tests are running. Jenkins really didn't appreciate the network issue yesterday.
[08:24] <rickspencer3> heh
[08:24] <rickspencer3> coolio jibel
[08:24] <rickspencer3> thanks a million
[08:25] <jibel> rickspencer3, a citation from a former french president for this week: 'les merdes volent toujours en escadrille'
[08:25] <jibel> rickspencer3, ask your french teacher for a translation ;)
[08:25] <rickspencer3> hehe
[08:26] <rickspencer3> the flying shit always is always something?
[08:36] <jibel> rickspencer3, yeah, less vulgar translation than the french citation would be something like "troubles come in packs"
[08:36] <jibel> rickspencer3, escadrille = squadron of aircraft
[08:36] <rickspencer3> hehe
[08:36] <rickspencer3> ah
[08:37] <rickspencer3> so, I'm not too bumbed I don't know "squadron" yet :)
[08:56] <rickspencer3> jibel, speaking of squadrons of trouble ...
[08:57] <rickspencer3> it looks like software-center broke in precise some days ago
[08:59] <rickspencer3> jibel, there are a lot of software-center tests, could we had at least a basic subset to the daily desktop smoke tests?
[09:01] <jibel> rickspencer3, yes, that's something we can do. we also talked with pitti and gema to add a basic start/stop test of all the default desktop apps available from /usr/share/applications/ and installed on the system
[09:02] <rickspencer3> jibel, ok, maybe you can make some time to discuss with mvo?
[09:02] <rickspencer3> to rephrase, "when you get the time, perhaps you can discuss with mvo" ;)
[09:03] <jibel> rickspencer3, or "I'll get the time to discuss with mvo" :)
[09:04] <mvo> jibel: starting is one thing, it would also be cool to run the "make test" basicly in the s-c tree, if I can help in any way to make this happen, just let me know
[09:04] <rickspencer3> yeah, jibel there are some good tests already in there
[09:04] <rickspencer3> I think at least the ability to install and remove apps would be good for smoke testing
[09:04] <jamespage> jibel: pong
[09:04] <rickspencer3> and then running the whole test suite daily as well would be nice
[09:04] <jibel> jamespage, unping :)
[09:04] <rickspencer3> (since we have the tests)
[09:06] <jibel> jamespage, jenkins was not starting the tests automatically, I restarted it and now it's processing the queue. no more problem for the moment
[09:09] <jamespage> jibel: OK - as you state probably the network issue from yesterday
[09:09] <jibel> mvo, I didn't look at s-c's testsuite, would you have time for a call tomorrow morning, so I understand what it covers and what's useful to run as part of the daily smoke testing ?
[09:09] <mvo> jibel: sure
[09:10] <mvo> jibel: actually tomorrow morning I am not around, it will have to be the afternoon
[09:10] <rickspencer3> jibel, mvo could you both please aptdeamon to that discussion?
[09:10] <mvo> jibel: but I'm happy to help, essentially all it need is (bzr co lp:sofware-center; cd software-center/test; make)
[09:12] <jibel> mvo, ok, I'd like to make sure there's no overlap with the tool I'm writing as part of https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-upload-intermediary
[09:13] <mvo> jibel: aha, ok
[11:49] <jamespage> jibel: I need to up the default disk image size in ubuntu-iso-testing
[11:49] <jamespage> or make it configurable on a test-by-test basis
[11:49] <jamespage> any opinion?
[13:05] <gema> jamespage: what do you mean by up the default image size?
[13:06] <gema> jamespage: are our tests checking that atm?
[13:06] <jibel> jamespage, feel free to change the default size, it would be easy to make it configurable too using test_config
[13:06] <gema> jibel: is that code in https://launchpad.net/ubuntu-server-iso-testing ?
[13:07] <jibel> jamespage, that's a 2 lines addition
[13:07] <jibel> gema, no it's the project page
[13:07] <jibel> gema, the code is here https://code.launchpad.net/~ubuntu-server-iso-testing-dev/ubuntu-server-iso-testing/trunk
[13:08] <jibel> gema,  nitpicking ;P
[13:08] <gema> jibel: yep, I meant if that code was in that project x) thanks mr french perfectionist guy :P
[14:10] <alourie|laptop> gema, ping
[14:17] <jamespage> jibel: OK - test_config?
[14:18] <brendand> does anyone know an easy way to get python unittest to output junit xml?
[14:19] <brendand> or, what is the easiest way?
[14:19] <brendand> preferably something that doesn't involve rewriting stuff
[14:19] <jibel> jamespage, you can put a config file in ConfigParser format in the test profile directory and it will be loaded in run test
[14:19] <jibel> http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/ubuntu-server-iso-testing/trunk/view/head:/run-test.py#L264
[14:19] <jibel> *run-test.py
[14:21] <jibel> so you can redefine the disk size if you want a specific value for a test. But of course, if you want change it for all the test, just change the default value
[14:21] <jamespage> jibel: that would be neater
[14:21] <jamespage> I need a bigger disk just for the multi-lvm test
[14:23] <jibel> jamespage, then create a configuration files in multi-lvm directory (config is the default name, I'm not strong at name picking)
[14:23] <jibel> add a section [vm] for example
[14:23] <jibel> and a setting disksize
[14:24] <jibel> then in run-test.py load this value with get_config_value(test_config, 'vm', 'disksize')
[14:24] <jamespage> love it
[14:24] <jamespage> I can use that for the raid test setup as well
[14:24] <jibel> yes, you can change the vm definition this way
[14:41] <alourie|laptop> I hate touchpads!!!!
[14:41] <alourie|laptop> 1 hour of wiki work just busted
[14:41] <alourie|laptop> damn
[14:42]  * jibel hates wikis
[14:42] <alourie|laptop> oh no, it didn't bust!!
[14:42] <alourie|laptop> it was in another window
[14:42] <alourie|laptop> phew
[14:43] <alourie|laptop> I still hate touchpads. No laptop brings a good one
[14:43] <patdk-wk> same here, why I use thinkpads, atleast it's optional then
[14:43] <alourie|laptop> yea, how do they call it? finger mouse?
[14:43] <alourie|laptop> I like those
[14:44]  * alourie|laptop is on friends' compaq
[14:44] <samantha-jian> isometric joystick
[14:45] <samantha-jian> I disable the touchpad on my thinkpad
[14:45] <alourie|laptop> there's no mouse on this compaq other than touchpad
[14:46] <alourie|laptop> that react on sleeves by closing tabs in the browser
[15:00] <gema> alourie: pong
[15:35] <alourie> gema: are you still here?
[15:35] <gema> alourie: indeed
[15:35] <alourie> I wanted to brainstorm couple of ideas with you
[15:35] <alourie> its about the wiki
[15:36] <gema> ok, can you give me , whilst we are at it the guideline to create test cases wiki?
[15:36] <gema> :)
[15:36] <alourie> the guidelines?
[15:36] <alourie> ah, sec
[15:36] <gema> k
[15:36] <alourie> https://wiki.ubuntu.com/QATeam/TasksPrecise/TestCasesRewrite
[15:37] <alourie> and I'll get back in a sec
[15:39] <gema> k, ta
[15:44] <alourie> ok, I'm back
[15:45] <alourie> gema: I wanted to discuss a bit our wiki rewriting
[15:45] <alourie> first, thanks a lot for the comments
[15:48] <alourie> now, regarding the "Testing Team" - main idea there is the ISO testing activities. So I think we don't need it, as long as the content is merged into other page. And the idea of it is.
[15:49] <gema> so you think the testing team and the QA Team are the same people
[15:49] <gema> just different tasks?
[15:50] <alourie> yes
[15:50] <gema> ok, sounds like we need one or the other but not both
[15:50] <gema> do you think keeping the QATeam one is better?
[15:51] <alourie> yes, because it gathers all stuff around QA, not just ISO testing
[15:52] <gema> ok, so maybe to make it clearer we need to put the isotesting stuff on a page  called iso testing
[15:53] <alourie> there is such a page
[15:53] <gema> then the testing page would b redundant
[15:53] <alourie> https://wiki.ubuntu.com/Testing/ISO
[15:53] <gema> can you keep a list of the pages that are redundant/obsolete so that when we move your content we remove them?
[15:53] <alourie> sure
[15:54] <gema> thanks
[15:54] <alourie> that would mean, btw, that the page above would move to QATeam/ISO
[15:54] <gema> yep, the iso testing one also needs rewriting
[15:54] <alourie> indeed
[15:54] <gema> let's take one step at a time , a top down approach, let's get the root right (QATeam) and drill down
[15:55] <alourie> I feel that there's a dependency tree that needs rework
[15:55] <alourie> sure thing
[15:55] <gema> indeed
[15:55] <gema> maybe we should do that, think of the structure
[15:55] <alourie> ok, good point
[15:55] <gema> and then shuffle the content around or remove it as we see fit
[15:55] <alourie> agreed
[15:56] <gema> so far I have QATeam and QATeam/AutomatedTesting
[15:56] <alourie> and there's Testing
[15:56] <gema> the automatedtesting one is up to date because I have been editing it
[15:56] <gema> yep, but we said that one is redundant
[15:56] <alourie> yes, but it has subpages
[15:56] <alourie> such as ISO
[15:57] <gema> yep, we need to recover those
[15:57] <alourie> which should be moved to, say, QATeam
[15:57] <gema> yep
[15:57] <alourie> that's why I said dependency tree :-)
[15:57] <gema> ok, let's go for that
[15:57] <gema> have you an idea of what it would look like?
[15:57] <alourie> and there's Kubuntu/QA, and probably something for Xubuntu as well. Should we unite them too?
[15:57] <alourie> and join us?
[15:58] <gema> I don't see why not
[15:58] <gema> if they agree
[15:58] <alourie> not completely yet. I'm still working on the root page, so I hope it becomes clearer as I progress with it
[15:58] <gema> alourie: ack, I will let you get on with it and have a good look at the test cases page
[15:59] <gema> alourie: do you prefer that I send you comments or that I change stuff on the wiki itself?
[15:59] <alourie> I'm almost happy with it now,  btw, after incorporating your comments
[15:59] <alourie> ahm
[15:59] <alourie> I don't mind you changing things
[15:59] <alourie> just let me know if you do
[15:59] <gema> ok, will let you know when I am done , I am going to do it now
[15:59] <alourie> great
[15:59] <alourie> thanks
[15:59] <gema> np
[16:00] <alourie> so, I'll continue working on root wiki page, and let you know on list when I'd like another feedback session
[16:01] <brendand> mvo - have you and the swc developers considered instrumenting the unittests with junitxml, so that jenkins can give a detailed report?
[16:01] <brendand> mvo - slash, are you running jenkins?
[16:02]  * alourie is adding 'create dependency tree graph' to tasks
[16:03] <mvo> brendand: not yet, but we want to do both, I will take with jibel tomorrow how we can do that
[16:03] <mvo> brendand: is it easy to enable the junitxml with unitest, haven't looked into this yet
[16:07] <brendand> mvo - unfortunately it seems to require modifying the test. about 6 extra lines, including the import
[16:09] <brendand> mvo - e.g. http://paste.ubuntu.com/771264/
[16:09] <brendand> mvo - could be scripted probably
[16:10] <brendand> mvo - assuming unittests have been written pretty uniformly
[16:11] <jibel> mvo, "profile: profile/main-all-amd64 worked"
[16:11] <jibel> mvo, \o/
[16:11] <jibel> 5 hours to play main-all and main-all-amd64
[16:13] <gema> alourie: I am done with the guide
[16:13] <alourie> k
[16:13] <alourie> thanks
[16:26] <gema> np
[16:27] <mvo> jibel: !!!!
[16:27] <mvo> brendand: thanks, looking
[16:46] <gema> alourie: do you mind that I put you against a wiki task on the blueprints?
[16:46] <gema> alourie: that way your work shows up with the rest of our workload
[16:46] <gema> kalosaurusrex: same with your ISO testing work
[16:49] <gema> I will ask on the list
[17:05] <brendand> mvo - some screenshots for you. http://people.canonical.com/~brendan-donegan/swc-jenkins/
[17:07] <mvo> brendand: nice
[17:12] <mvo> brendand: thanks a bunch, I check it out after dinner
[17:12] <mvo> brendand: check it out futher I mean :)
[17:12] <brendand> mvo - and you can pack up the coverage reports and attach them to the build :)
[17:12] <brendand> tis awesomeness
[17:15] <mvo> yeah, that as well
[17:15] <mvo> !!!
[17:15]  * mvo is excited
[17:25] <stgraber> jibel: not sure if you spotted that today but I messed up casper a bit yesterday causing some error messages to show up on the reboot prompt (please eject the CD, ...)
[17:26] <stgraber> jibel: I'm fixing that now so next dailies should be looking good again (the error doesn't break anything, it's just ugly ;))
[17:27] <gema> brendand: that plugin looks good
[17:27] <gema> brendand: where did you get those tests from?
[17:30] <brendand> gema - in software-center
[17:30] <brendand> gema - no plugin needed. jenkins parses junit natively
[17:30] <brendand> gema - the tests need to be modified to output junit, but it's a few lines of code per test
[17:30] <gema> brendand: have you tried python unit?
[17:31] <gema> brendand: is the output any similar?
[17:31] <brendand> gema - well, pyunit is based on junit, but by default the output isn't xml
[17:31] <brendand> gema - so you just have to make it output xml
[17:32] <gema> brendand: ack, I am going to look into that
[17:32] <brendand> gema - if i could do this on a public jenkins instance then everyone could see it
[17:32] <brendand> gema - i think i need to ask my isp for public ips. what a pain
[17:32] <gema> brendand: the public instance of jenkins is managed by IS
[17:32] <brendand> gema - but i can create jobs on it, right?
[17:32] <gema> brendand: you could have a domain always informed of your ip
[17:32] <brendand> or i need a ticket for each job/change to a job :)
[17:32] <gema> brendand: we have that here and it works wonderfully
[17:33] <gema> brendand: but you need to tinker with your router
[17:33] <brendand> gema - yeah, that's the thing. i need to find the password again :)
[17:34] <gema> brendand: haha, talk to you when I have my jenkins instance running, we may be able to publish from mine
[17:34] <gema> I have all that setup
[17:34] <gema> brendand: but my router has got a problem that I have been ignoring for weeks now, need to reinstall it this weekend :)
[19:27] <patrickmw> brendand, hey do you need jenkins assistance?
[19:28] <patrickmw> brendand, the public instance is read-only and never actually runs jobs
[19:28] <patrickmw> brendand, we use a few private instances that push results to jenkins.qa.ubuntu.com
[19:29] <brendand> patrickmw - i'd just like a playground where other people can see what i'm doing
[19:29] <brendand> (weird sentence)
[19:29] <patrickmw> brendand, I gotcha though
[19:31] <patrickmw> brendand, the private instances can be used as a sandbox to test jobs.  But there are rules.  For example, depending on what type of tests you are running you will need a system to run tests on.  VMs are easiest if that will do.
[19:31] <patrickmw> brendand, the master instance does not run tests so security and as not to fubar the server
[19:32] <patrickmw> brendand, another issue is that the labs are behind IS controlled firewalls
[19:32] <patrickmw> brendand, if you need access to ports that are not open you will need to open a ticket
[19:53] <brendand> patrickmw - vm will do fine
[19:54] <brendand> patrickmw - where do i go?
[19:55] <patrickmw> brendand, this is something that will require configuration from the lab admin
[19:56] <patrickmw> brendand, for now please send and email to qa-team with your VM requirements and how you intend to use jenkins so we can get you set up as easily as possible
[19:57] <patrickmw> there is quite a backlog, but since we have a full time admin now things will pick up quickly
[19:57] <brendand> qa-team@?