17:00:29 #startmeeting QA Meeting 17:00:29 Meeting started Wed Nov 30 17:00:29 2011 UTC. The chair is gema. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. 17:00:29 17:00:29 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 17:00:46 hi everyone and welcome to the new QA meeting 17:01:05 I have seen jibel, nuclearbob and charlie-tca already present, anyone else? 17:01:15 * phillw is here :) 17:01:23 o/ 17:01:32 hi phillw and patrickmw ! 17:01:52 ok, so we will get started and welcome anyone that joins later 17:02:06 * alourie is present 17:02:15 since this is a new meeting, we don't have previous actions (hi alourie :) 17:02:15 but only as a listener for now 17:02:21 alourie: no problem 17:02:23 gema: no problem 17:02:28 and hi 17:02:44 let's get on discussing the agenda from now on 17:02:52 #topic Discuss new agenda 17:03:20 you can see a proposal of agenda that I put together for today in the meeting page: https://wiki.ubuntu.com/QATeam/Meetings 17:03:41 this is just for today, but I think the blueprints update is something we should keep 17:03:53 do you guys have more topics to add to the agenda? 17:04:50 charlie-tca: would you like to have a section where you give an update regarding the testing for your distro? 17:05:06 if so, how shall we name that item? 17:05:23 Not today 17:05:31 ok, but going forward? 17:06:07 If it will be benificial to know what the Xubuntu tests show, yes 17:06:42 we can do the same for lubuntu, if our team wishes so (we have a meeting tonight, so I will ask their views). 17:06:44 I believe it is important to see the correlation yes 17:06:53 ok, phillw 17:07:21 so I will add a section for status of the different derivatives as well as for Ubuntu 17:07:32 well, for now for Xubuntu and lubuntu 17:07:34 I cut a finger bad yesterdAY, am only partly here today 17:07:45 charlie-tca: I am sorry to hear :( 17:08:03 sorry to hear charlie-tca :( 17:08:04 Thanks. Will do my beST ANYway 17:08:16 no worries, we read you very well, take care :) 17:08:59 #action gema to add lubuntu and Xubuntu testing updates to the agenda 17:08:59 * meetingology gema to add lubuntu and Xubuntu testing updates to the agenda 17:09:12 anything else you'd like to add/remove from the current proposed agenda? 17:10:33 ok, so we'll leave there for now and review it as we go along, then 17:10:54 #topic Blueprints Update for Precise 17:11:13 now we'll go through all the blueprints that we are working on and give a quick update on them any questions fire as we go along so that we don't lose context 17:11:26 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing 17:11:40 we have made available this page for everyone to see Precise automated testing results: https://jenkins.qa.ubuntu.com/view/Precise/ 17:11:52 patrickmw: do you want to explain briefly what is there? 17:12:03 sure 17:13:10 currently there are the automated ISO installer tests, DX unit tests, unity merge tests, boot speed tests and I'm sure I'm missing something 17:13:25 more builds get added weekly 17:13:35 ah upgrade tests 17:13:39 o/ 17:13:46 go ahead, alourie 17:14:13 is there a way to see these tests? To find out what is being done and how to participate in them, if possible? 17:14:23 to contribute? 17:14:24 .. 17:14:29 yes 17:15:08 I don't there is a central location, but we can list the launchpad projects on the wiki 17:15:19 that'd be great 17:15:43 can I give you an action to compile that list to you patrickmw? 17:15:46 yes 17:16:11 o/ (question for alourie ) 17:16:15 jibel: sure 17:16:20 #action patrickmw to publish a list of launchpad projects that conform our automated testing in jenkins 17:16:20 * meetingology patrickmw to publish a list of launchpad projects that conform our automated testing in jenkins 17:16:27 go for it jibel 17:16:44 which type of tests would you like to contribute to ? 17:17:02 iso testing, package testing, ... ? 17:17:40 jibel: well, anything. I just want this all to be as transparent as possible for possible contributors to join 17:17:51 me including 17:17:57 ok thanks 17:18:22 I would be probably good for ISO testing 17:18:35 but others may be more apt for other types 17:18:39 .. 17:18:55 excellent, alourie, thanks for the idea and for wanting to contribute 17:19:01 we need as much help as we can get 17:19:04 sure 17:19:25 so there is more stuff going on in this blueprint.. let me see 17:19:36 we are in the process of updating the documentation to be able to interpret the results and troubleshoot failures (information available in the blueprint) 17:19:55 we also are working on a new tagging scheme that will allow us to assess the quality of the automated testing, we are going to start using 17:20:04 in the canonical-platform-qa team, these tags for the automated testing: https://wiki.ubuntu.com/QATeam/AutomatedTesting/TestingTypeAndBugTracking 17:20:25 we want to make sure we can assess the quality of these tests we are going to be running and improve them over time 17:20:37 that's all I have, anything else anyone? 17:21:01 good, moving on then 17:21:09 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-boot-speed-testing 17:21:14 patrickmw ? 17:21:24 * Results available here: http://reports.qa.ubuntu.com/reports/boot-speed/ 17:21:24 * Jobs available here: https://jenkins.qa.ubuntu.com/view/Precise%20Boot%20Speed/ 17:21:25 * Job failures due to NFS boot breaking on yesterdays ISOs. Bug submitted. 17:21:25 * Currently generating benchmark bootcharts for each system (lucid, maverick, natty, oneiric) and they will be available on the Boot Speed Report this week 17:21:25 * Following up on NFS Boot bug and will try to run boot speed tests today 17:21:36 .. 17:21:55 cool, let's give some time to people to read in case there is any question 17:22:22 nothing.. then moving on 17:22:30 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-kernel-sru 17:22:41 hggdh: do you have an update on this? 17:23:08 * alourie has to leave to put the baby to sleep, hopefully get back in time. :-) 17:23:52 what I know is what is on the blueprint, that sconklin is working on running rteval tests and trying to package them 17:24:06 I will try to get more feedback for next week 17:24:19 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-standard-sru-testing 17:24:23 jibel ? 17:25:07 nothing from me on this topic this week 17:25:12 ok 17:25:20 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-test-case-management-tool 17:25:46 jibel installed an internal instance of litmus and we are evaluating its viability to use for handling our test cases, 17:25:56 we are in the process of setting up an instance that the community can also use and evaluate but we are undergoing review of the tool, etc, by the IS team 17:26:23 it will hopefully be ready soon and we will let you know in this meeting 17:26:37 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-qa-regression-testing 17:26:40 nuclearbob: ? 17:27:19 I've got an autotest package building in my ppa 17:27:55 I'm getting that improved and tested on openstack instances, once we get the new lab hardware in, we should be able to get those tests running automatically on new instances ona regular basis 17:28:07 and we can get xml output from that to feed into jenkins 17:28:21 so we will be able to see results in jenkins then 17:28:28 yep 17:28:33 excellent, thanks 17:28:39 anything else from you? 17:28:42 nope 17:28:54 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-automated-test-submissions 17:29:01 patrickmw: ? 17:29:11 work has started, nothing to report 17:29:21 ok, thanks 17:29:37 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-backlog 17:29:48 this blueprint is to keep track of all sorts of bits and pieces that we are doing but are not part of the big items we are working on 17:29:56 if there is any question please send us an email and we'll address it 17:30:03 amongst other things we are going to be rewriting the bits and pieces that are obsolete in the ubuntu QA wiki, if anyone wants to collaborate, 17:30:12 you are more than welcome! 17:30:28 just let us know so that we can coordinate the effort 17:30:38 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-test-case-definition 17:30:46 we discussed a test case definition at UDS and I proposed it to the CoP in canonical, they were happy with it and decided to embrace 17:30:56 that test case definition and start using it widely 17:31:02 so any test cases from now on will probably have that format 17:31:14 this blueprint is finished now, so I will make it disappear from our list of topics to discuss 17:31:15 o/ 17:31:20 go ahead, charlie-tca 17:31:39 Is that format available somwplace for community to use? 17:31:49 indeed, just a sec 17:32:05 https://wiki.ubuntu.com/QATeam/TestCase 17:32:20 Thank you 17:32:29 we will be putting all the links to all the new content in place, because the wiki is becoming very difficult to navigate 17:32:33 no problem 17:32:49 #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-metrics 17:33:00 we haven't started working on this yet, so nothing to report this week 17:33:15 that is it in terms of blueprints, now the big topic of the week 17:33:22 #topic Alpha-1 Testing 17:33:29 jibel: ? 17:34:02 alpha 1 is due tomorrow, coverage could be better, here it is: 17:34:11 Edubuntu 50.00% 17:34:11 Kubuntu 5.56% 17:34:11 Lubuntu 42.86% 17:34:16 Mythbuntu Untested 17:34:20 Ubuntu 56.63% 17:34:20 Ubuntu Server 80.00% 17:34:20 Xubuntu 50.00% 17:34:33 For Ubuntu, architectures mac and powerpc are untested which explains the low coverage. 17:34:45 Derivatives (especially Kubuntu) need your help for A1 testing. 17:34:51 No release blocker bug found at the moment. 17:35:04 The list of defects is available at http://91.189.93.73/qatracker/reports/defects/opened 17:35:30 One is particularly annoying (bug 894768) it's easily reproducible in VMs but we have one report where it fails on hardware. 17:35:31 Launchpad bug 894768 in linux (Ubuntu Precise) "Installation randomly fails with: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 621, in copy_file targetfh.write(buf) IOError: [Errno 22] Invalid argument " [High,In progress] https://launchpad.net/bugs/894768 17:35:45 If you've spare hardware and can install Ubuntu Precise Desktop _i386_ on it, then you can try to confirm this bug. that would help a lot. 17:36:14 For this milestone we are using a new version of the iso tracker rewritten in Drupal 7, thanks to stgraber 17:36:26 Details on ubuntu-devel mailing list https://lists.ubuntu.com/archives/ubuntu-devel/2011-November/034495.html 17:36:31 .. 17:36:33 questions ? 17:36:40 or comments 17:37:36 doesn't look like it 17:37:40 thanks for the update, jibel 17:37:53 help 17:37:59 ignore... 17:38:13 ok... 17:38:26 so moving on 17:38:33 #topic Other Topics 17:38:48 any other topics or issues you'd like to bring up? 17:39:33 regarding the chairing of the meeting, I think we shouldn't force people to do it with a shuff 17:39:44 if someone wants they can, if not, I will be doing it 17:40:03 or if I am not able to , I hope someone will volunteer :D 17:40:20 but I think forcing people to chair may have detracted some collaborators from showing up 17:40:23 just a theory 17:40:55 gema: I'll cover chairing if needed in an emergency :) 17:41:00 I will try to put an agenda that makes sense for next week and then I will offer the chairing of the next meeting in case anyone wants to do it the week after next 17:41:04 thanks a lot, phillw :) 17:41:35 ok, so any thoughts regarding the new format, better, worse, are we missing anything? 17:41:55 its good 17:41:58 yeah 17:42:09 I think if we're missing anything it'll come up and we can add it 17:42:25 yep, I am very glad that so many new faces were here today 17:42:38 +1 17:42:52 let's keep the momentum going and see if we can build a good QA community around this meeting :) 17:43:11 thank you everyone for your time, see you next week! 17:43:46 #endmeeting