=== zyga_ is now known as zyga === yofel_ is now known as yofel === _salem is now known as salem_ === cr3_ is now known as cr3 === cr3 is now known as Guest64961 [16:20] balloons, do you think it'd be worth adding a step to verify suspend/resume as a post-installation test for desktop ? [16:21] like suspend/resume must succeed 5 times in a row [16:21] jibel, wow.. 5 times [16:21] 10 ? [16:21] I think suspend/resume is always a rocky thing [16:21] it depends if we will be aggressive to support suspend/resume failures [16:22] personally I don't suspend/resume ever on my desktop.. and my netbook has perfect ubuntu support (i bought it for that reason), so suspend/resume does work [16:22] but otherwise I don't suspend/resume [16:22] that includes any os.. lol [16:23] I've been stuck with windows and macbooks at points in my life, and they also would sometimes fail [16:23] it's really sad [16:23] just randomly not wake up.. [16:23] lol -- I guess I've ranted. Long past your question. I think it's better to be tested in kernel testing [16:24] balloons, hm, it be nice if we could collect data, but I think suspend/resume is a critical feature of the OS [16:24] but yes, we should have it.. and we do in the kernel testing. But we're doing the LTS kernel testing, not for the dev version [16:24] when you commute do you shutdown your laptop ? [16:24] I just close the lid [16:25] I just close the lid -- it's a chromebook and everything works perfectly [16:27] I'm asking because we just had a regression in 3.5.0-5 [16:27] at least we should be able to detect it in the dev release during milestone testing [16:28] yes, if you notice, it was noticed by the kernel testing: http://packages.qa.ubuntu.com/qatracker/milestones/223/builds/19062/testcases/1306/results [16:28] I wanted to start something similar for the dev version [16:30] I did an experiment with software-properties when it landed: s, if you notice, it was noticed by the kernel testing: http://packages.qa.ubuntu.com/qatracker/milestones/223/builds/19062/testcases/1306/results [16:31] the idea is to track certain packages (critical things, and critical desktop components) and test them throughout the development release === Guest64961 is now known as cr3 === cr3 is now known as Guest9828 [16:33] balloons, or maybe we could have a run once test case like desktop-extra that covers critical packages during milestone tesitng ? [16:33] I mean a test case which is not about testing if the image is installable but if everything runs properly after install [16:35] jibel, ahh -- yes, well we could incorporate the testing into the milestone sure [16:35] I mean, add some optional testcases to our desktop image for stuff we care about [16:35] that can include kernel [16:35] eays [16:36] we have a REALLY basic version of it on our testcases now [16:36] aka, check the arch and open firefox [16:36] I think thats pretty much it === zyga is now known as zyga-brb [16:39] jibel, would you care to meet up and discuss in more detail? I have a couple comments I wanted to make on the current tests anyways [16:39] I think we could separate it from the installation. because 1. it would affect all types of installations 2. it affects specific packages not the components of the installer. [16:39] balloons, sure [16:40] 3. that would make the current test clearer, installer test cases test the installer, post-installation tests test the packages [16:40] well, the result of the installation === zyga-brb is now known as zyga-afk === Guest9828 is now known as cr3 === cr3 is now known as Guest1039 [17:39] balloons: ping [17:40] phillw, ponh [17:41] hi balloons, I hope you had a good weekend. Do you have an E.T.A. for the A3's to land at http://iso.qa.ubuntu.com/qatracker/milestones/226/builds ? [17:41] I asked skaet earlier -- she said they would be switching sometime today [17:41] not sure why it hasn't happened yet [17:42] well.. lol [17:42] balloons, 2100 UTC is the standard time. [17:42] they are building [17:42] balloons, what's building right now is the standard cron dailies [17:42] ohh skaet while I have you.. I always forget the std nightly build time [17:43] skaet: thanks, I'm just about to pen the e-mail to lubuntu-general letting them know :) [17:43] what is it in UTC? [17:43] 2100?? [17:43] I thought it was 0200 UTC [17:43] skaet: yup, he had me thinking :) [17:44] phillw, btw, I want to land a final version of that wiki page today [17:44] I'm gonna push for it [17:44] balloons, phillw, we're waiting on a kernel drop and d-i, so may even be a bit later than that. Probably at least one more after this first set though for some other updates. [17:45] balloons: can you post me the link again, please? [17:45] https://wiki.ubuntu.com/QATeam/GettingInvolved [17:46] hmm [17:46] that doesn't seem right [17:46] https://wiki.ubuntu.com/QATeam/GettingInvolved/MoreInfo [17:46] ahh there it is [17:48] balloons: are you happy enough with MoreInfo for it get a mention on the parent page? [17:48] phillw, that was the point, I wanted to land it and link it today yes [17:49] however, I wanted to go through it again [17:49] we'll be communicating again I'm sure :-) [17:49] I have more stuff to add -- some answers to questions people sent [17:49] skaet: So, If I say 00:01 24th July - is it expected that they will all be there by then? [17:50] with the proviso of we exepect a respin during the A3 QA stage? [17:51] phillw, no, all won't have finished building by then, even if we did start at 2100, which its likely to be later [17:51] balloons: that is the wonderful thing about MoreInfo, our testing page started off quite short, but has grown due to FAQ's. Each time we get new members, it tends to have another topic added :) [17:51] I'd set the expectation that there will be an initial set showing up aroun 0600 UTC on the 24th, and a respin later that day [17:51] jibel, sent you an invite for tomorrow [17:52] okies skaet, this does really trim down the QA window! Are we still committed to Thursday? [17:52] phillw, however data on the first set, catastrophic failures, etc. is going to be useful in avoiding later respins. [17:54] phillw, it may end up being just one set, all depends on when some builds/etc. finish. [17:54] just don't want folks surprised if the builds don't align. :/ [17:54] skaet: as we still have bug 1007394 which is unresolved, that one will grumble on. [17:54] hmm, someone stolen the bug bot? [17:54] Launchpad bug 1007394 in mdadm (Ubuntu) "Quantal daily fails to complete installation" [High,Confirmed] https://launchpad.net/bugs/1007394 [17:55] Okies, thanks for the heads up. I'll phrase it the best I can :) [17:58] phillw, thanks for flagging, adding it to the pad === zyga-afk is now known as zyga [18:24] skaet: balloons you should get a copy of it via your lubuntu-qa mailing list link. Please let me know if there is anything factually incorrect :) === Guest1039 is now known as cr3 === cr3 is now known as Guest88086 [19:13] AlanBell: ping === Guest88086 is now known as cr3 === cr3 is now known as Guest21652 === sergiusens_ is now known as sergiusens === salem_ is now known as _salem [21:32] balloons: ping [21:32] phillw, howdy [21:32] man what a monday [21:32] these mondays are always crazy my friend [21:33] are you excitied? I feel like I could run a marathon right now! [21:33] hi balloons, I've had a chilled out Monday. Had a brill w/end so left the computer alone today until about 7pm :) [21:33] Now I'm playing catch up. [21:33] * hggdh wonders about balloons' sanity [21:34] balloons: just a little ask, if I may? [21:35] phillw, of course [21:35] hggdh, mwahahahha [21:35] balloons: I was almost set to welcome you to the madhouse ;-) [21:35] (from inside, of course [21:36] welcome back my friend/ to the show that never ends/ we are glad to have you here/ come inside, come inside (and so on) [21:37] (clue: karn evil 9, ELP) [21:37] balloons: would you cc the lubuntu-qa@lists.launchpad.net, mailing list. It just saves me forwarding the emails. [21:38] that way, even when I'm not about - they get the latest information. [21:39] phillw, ;-) for the iso testing stuff only perhaps? [21:40] balloons: yes for that, or for anything urgent you think they should be made aware of. [21:40] alright, I will try and integrate that into my thought process [21:40] :-) [21:41] thanks, they do appreciate being kept "in the loop" :) [21:42] np.. [21:51] balloons: they also have a track record of responding to an SOS for a different member of the family being tested. Honest Nicholas, L-QA do not bite - several of them test across platforms already. [21:51] phillw, I know this to be true [21:51] they are wonderful, and I've seen them help rally around a flavor in the past to help test the release [21:52] bah that ctrl+w [21:53] As has just happend with another project, it was the feeling of being treated like a mushroom that caused problems. If I ever get a complaint from L-QA about "too much information" we can look into it. Until then, if it involves QA - please cc them :) [21:57] balloons: drat, just been chatting to LordOfTime about his transfer of ZNC over, forgot you wanted to have a chat with him :( [21:57] phillw, I caught him one day [21:57] conversation has been had :-) [21:58] balloons: great. an update is he did the transfer last night, and so it should all be up and running within the next day. [22:01] he has sorta apologised to me over the fact it would not run on a rpm system (CentOs), as he has a load of problems with the Ubuntu server system :P [22:01] Linux == Linux :) [22:02] on the plus side. I'll set him up an centos system, so he can port it to that arch. [22:03] so it won't run on rpm eh? [22:06] balloons: it appears that what he thought was the problem was not an rpm problem, hence the semi apology off him :D [22:08] As ZNC is a 'project' I'm quite happy to let him have a CentOS area to play with. Whilst 'Upstream' is just that, it does not mean that I should negate offering those projects an area to live on. [22:09] The ZNC coming online is on Ubuntu Server 12.04 [23:23] balloons: do not be afraid, ZNC server is just coming back on line in its new home :) [23:24] Lord of Time is on #sii if you want to catch him. [23:39] gema: We've talked about running the piglit Mesa regression suite on the QA lab hardware a couple of times at UDSes. I'd like to start driving that to implementation :)