[07:06] morning! [08:22] Morning All [08:24] morning davmor2 [08:47] ara: how did it go Monday in the end. We were on holiday and the sites wifi was down so I couldn't join in :( [09:11] davmor2: you don't test on your holidays!! [09:23] ara: Not without wifi I don't no :( I was however using my netbook which has UNR Jaunty on it found a couple of issue that I'm going to write up now I have wifi :) [09:32] * ara reboots === asac_ is now known as asac === eeejay is now known as eeejay_hummus === eeejay_hummus is now known as eeejay [12:36] * ara -> lunch [12:43] hino ping [12:43] jtholmes: who hino [12:44] jtholmes: if your after heno he doesn't seem to be on irc and therefore wont see your ping anyway :) [12:46] sorry mistype heno is who i wanted thanks [12:46] davmor2, who is in charge of testing when heno is away [12:47] jtholmes: just ask [12:47] who is in charge of testing in heno's absence [12:48] jtholmes: sorry I meant ask what you were going to ask heno someone should be able to point you in the right direction [12:50] ok [12:52] The Use weak password dialog in the installer has the sense reversed, cjwatson made a text change last night but the sense of the choice is wrong and there really isn't a quesiton associated with the dialog [12:52] reversed=reversed [12:52] watson did not change the sense only the button text [12:53] jtholmes: the yes no on use weak password [12:53] correct the yes no [12:54] it is a question. It asks if you want to use the weak password and then tells you what length the strong password should be. [12:54] no leaves you in the dialog to change your password yes takes you to Ready to install [12:54] that's correct [12:56] jtholmes: the question if you look at it asks "use weak password?" so yes will continue the install and no will take you back to the password section so you can change the password. I don't see anything wrong with that behaviour [12:56] cjwatson: ^ [12:58] well then the last part of the user information should say 'Do you want to choose a stronger password?' Not ' You should choose a stronger password' === thekorn_ is now known as thekorn [13:00] it really dosen't ask 'use weak password' [13:00] it makes a statement 'You should choose a stronger password' [13:02] jtholmes: you might want to take it up with the installer team [13:02] who would that be please [13:03] #ubuntu-installer [13:03] davmor2, ok thanks [13:13] jtholmes: don't call me "Watson", by the way, it's rude to just use a surname [14:26] schwuk: ping [14:31] schwuk: on system testing is there a way to return focus to the 'type text' window and away from the running test window. Currently if you type text nothing happen until you put focus back on the type text window. [14:58] cr3: Morning [14:58] cgregan: Morning [14:59] davmor2: Morning [14:59] davmor2: ahoy, matey! [14:59] cr3: I asked schwuk this but I'll ask you too on system testing is there a way to return focus to the 'type text' window and away from the running test window. Currently if you type text nothing happen until you put focus back on the type text window. [15:00] cr3: Is it talk like a pirate day again already :) [15:00] davmor2: I like that kind of concern, might you know off hand how to do that in gtk? [15:00] davmor2: I wish every day was talk like a pirate day :) [15:02] cr3: I have no idea what-so-ever I don't know if it's possible that's why I was asking here first before posting a bug :) [15:04] cr3: could you not make the type text window open after the test running window? [15:31] davmor2: could be interesting to address... [15:33] schwuk: or just change the title to "click and type text" :) [15:34] davmor2: but that would be testing both the mouse and the keyboard :) [15:34] davmor2: bug? :) [15:35] schwuk: I was finding out if it was possible to do before writing one. Not being a programer :) [15:36] davmor2: of course filing a bug doesn't infer that we'll fix it... [15:36] :D [15:37] davmor2: in theory it's possible, so if you can file a bug, I'll try and address it [15:38] writting as soon as the page comes up :) [15:49] schwuk: bug 353190 [15:49] Launchpad bug 353190 in checkbox "Jaunty: in checkbox-gtk on keyboard text simply typing displays nothing" [Undecided,New] https://launchpad.net/bugs/353190 [16:41] Hello heno [16:41] hey davmor2 [16:43] alternate has gained a new progress meter which is nice. The bar still sticks at 6% but you see the text read accessing 1 of 191 etc yay :) [16:46] * ara takes a break before the meetings [16:48] heno is the qa meeting on "#ubuntu-meetings" in about 10 mins? [16:49] jtholmes: It's 17 00 UTC, which is in 70 minutes [16:49] jtholmes: that be about an hour an 10 minutes [16:49] ok wasnt sure of the time diff thanks [16:49] np [16:57] davmor2, thanks didnt see your msg [16:57] afk [17:43] bdmurray: congrats [17:43] davmor2: thanks! [17:58] davmor2 is the #ubuntu-meetings on freenode or elsewhere [17:58] #ubuntu-meeting [18:00] Ubuntu QA Meeting in ~1 minute at #ubuntu-meeting [18:01] davmor2, thanks had s on meeting [19:01] davmor2 what does UDS stand for Ubuntu ?? [19:02] jtholmes: ubuntu developer summit [19:03] thanks [19:32] eeejay: will you join the dt call? === fader_ is now known as fader|lunch [19:33] heno, yup [19:35] eeejay: (we are dialed in) [19:37] https://wiki.ubuntu.com/Testing/Automation/Desktop/Coverage [19:43] http://package-import.ubuntu.com [19:48] ara: maybe we could somehow grab all the test XML files, append them to a giant file, and do some xslt magic that will give a current picture of coverage? [19:48] maybe i am complicating stuff [19:50] eeejay: :D [19:58] eeejay: Plase take a look at the parse_suite.py located in the scripts subdirectory in the urn branch. I parses a module file and generates the XML file based on the information in the XML file. [19:58] eeejay: I added also an option to generate wiki output with the same information [19:59] jcollado: cool! [19:59] eeejay: I believe it could be extended to get something similar to XSLT [20:00] jcollado: i am thinking, it could be in the main executable with a "--coverage" flag. [20:00] eeejay: I meant "based on the information in the python module" [20:00] jcollado: that way it could grab all the suites [20:00] eeejay: Yes, that could be done also [20:03] jcollado: my thought was to parst the suite XML file, where all the human readable name/descriptions reside [20:04] jcollado: docstrings won't be good for that purpose because one method could be used for many test cases, same with class [20:04] eeejay: You're right. What I thought that could be done in such a case [20:05] eeejay: is just create a helper method in call it twice from different testing methods [20:05] jcollado: hah [20:05] eeejay: being a testing method one that matched the testing method pattern (i.e. r'^test' regexp) [20:06] jcollado: that is originally how i was designing it too [20:06] eeejay: I feel is nice to write the information only in one place instead of splitting it in different files. Don't you think so? [20:07] jcollado: yeah, that is why we are not using the docstrings :) [20:07] jcollado: the XML file is "canonical" [20:09] eeejay: He, he. It's a matter of taste. I don't like much XML files. I prefer everything in the code to keep the documentation and other information in sync with the code. [20:10] jcollado: i generally agree with you [20:18] sbeattie: I commited a fix for update-manager-text crash, please let me know if it reappears (but it should be fixed) [20:20] mvo: cool, thanks! BTW, I'm not sure how it easy it to steer newt from python, but it might be nice to have it size things sensibly depending on the terminal settings. [20:21] sbeattie: good point [20:21] sbeattie: probably not jaunty though :/ [20:23] yeah, not surprised. but wishlist it for me, okay? :-) === fader|lunch is now known as fader_ [20:45] sbeattie: promised :) [20:45] sbeattie: poke me on UDS if nothing is done until then [20:46] heh, sure thing; I'm likely to keep using it. [20:47] nice [20:47] * mvo waves good night === mathiaz__ is now known as mathiaz === Rocket2DMn is now known as Joeb545 === Joeb545 is now known as Rocket2DMn