15:00:03 <jlaska> #startmeeting Fedora QA meeting
15:00:03 <zodbot> Meeting started Mon Oct 11 15:00:03 2010 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:10 <jlaska> #meetingname fedora-qa
15:00:10 <zodbot> The meeting name has been set to 'fedora-qa'
15:00:14 <jlaska> #topic Gathering ...
15:00:36 * maxamillion is here
15:00:46 <jlaska> iirc adamw is out today ... canadian holiday
15:00:51 <jlaska> hey maxa!
15:00:59 <maxamillion> ($boss cancelled my conflicting meeting, so I finally get to attend a QA Meeting!)
15:01:03 * kparal 
15:01:04 * jskladan is here :)
15:01:11 * jsmith is travelling back from UTOSC, and will lose internet access shortly
15:01:24 <jlaska> kparal: jskladan: jsmith: greetings all
15:02:07 * jlaska whispers wwoods summoning spell
15:02:11 <mkrizek_home> I am here, I have to multitask though (math lecture:))
15:02:42 <jlaska> mkrizek_home: oh goodness :)
15:03:10 * adamw is definitely not here
15:03:21 <jlaska> adamw: you should be giving thanks!
15:03:28 <adamw> given 'em
15:03:30 <adamw> they were small
15:03:34 * jlaska figures that's just adamwbot responding
15:03:42 <adamw> *beep*
15:03:42 <jlaska> alright, let's get started
15:03:49 <jlaska> #chair kparal
15:03:49 <zodbot> Current chairs: jlaska kparal
15:04:08 <jlaska> kparal: hopefully no objections, but I may need your help closing out the meeting again
15:04:18 <kparal> of course
15:04:30 <jlaska> #info agenda available on the list -- http://lists.fedoraproject.org/pipermail/test/2010-October/094537.html
15:04:38 <jlaska> #topic Previous meeting follow-up
15:05:11 <jlaska> #info jlaska will ask Hurry whether adding some amount of installer validation or installer bug verification is possible
15:05:29 <jlaska> Hurry and Newgle are back from holiday, and will be jumping into the F-14-Final testing as planned
15:06:05 <jlaska> I'll save the remaining part of the action item for discussion shortly
15:06:21 <jlaska> basically just a ping to the list ot help work down our ON_QA queue and more
15:06:24 <jlaska> that's all I had from last week
15:06:31 <jlaska> anything I missed?
15:06:58 <jlaska> #topic F-14-Final Testing
15:07:28 <jlaska> adamw: I was assuming you'd be out today, but your welcome to talk through this
15:08:46 <jlaska> #info Oct 08 - blocker review meeting held last Friday (see http://meetbot.fedoraproject.org/fedora-bugzappers/2010-10-08/fedora-bugzappers.2010-10-08-15.59.html)
15:09:05 <adamw> i was really just hovering in case anything important comes up
15:09:09 <jlaska> okay ...
15:09:14 <adamw> but yeah, we had the blocker review, we have another next week
15:09:26 <adamw> we just did a RATS run (right?), and we have TC1 due tomorrow
15:09:34 <jlaska> #info Oct 07 - Fedora 14 RC acceptance test run planned (see rel-eng ticket#4140)
15:09:40 <fenris02> the tc1 on alt.fp.o is pre-tc1?
15:09:52 <jlaska> yeah ... Newgle was out, so I'm collecting results now.  I've asked for his help to summarize testing to the list
15:09:56 <adamw> it was meant to me the acceptance test image
15:09:59 <adamw> s/me/be/
15:10:00 <jlaska> fenris02: it's incorrectly named TC1
15:10:06 <fenris02> ok, fair enough.
15:10:21 <jlaska> you're welcome to test it, but there will be a *real* TC1 landing this week
15:10:57 <jlaska> #info I pulled together a query of the MODIFIED and ON_QA F14Blocker and F14-accepted bugs -- http://tinyurl.com/3235yah
15:11:33 <jlaska> For folks looking for a relatively quick way to get involved and help move things forward, validating ON_QA blocker bugs is a good way to get started
15:11:51 <adamw> also, writing kernel patches
15:12:22 <jlaska> and as adamw notes, we have the scheduled TC1 release validation test run starting this week
15:12:33 <jlaska> #info Oct 12 - F-14-Final TC1 validation starts
15:12:45 <jlaska> adamw: kernel patches, that doesn't strike me as a low barrier to entry :)
15:13:00 <adamw> pfah, it's easy. they especially love submissions in Microsoft Word format
15:13:32 <jlaska> adamw: be sure to add the text "Reviewed by: awilliam"
15:13:44 <jlaska> okay, anything else on F-14-Final testing?
15:14:05 <adamw> not that I can think of
15:14:12 <jlaska> Please keep communicating issues and potential bugs to the list
15:14:29 <jlaska> alrighty ... next up ...
15:14:30 <jlaska> #topic F-14 Test Days
15:14:46 * jlaska notes ... just got a message from wwoods ... he's having VPN connection issues
15:15:10 <jlaska> #info Oct 14 - OpenLDAP with NSS - https://fedoraproject.org/wiki/Test_Day:2010-10-14_OpenLDAP/NSS
15:15:29 <jlaska> kparal: thanks for sending out a test day announcement ... quite early as well!
15:16:08 <jlaska> I still see a few FIXME's on the test day wiki page
15:16:17 <kparal> jlaska: the openldap guys wanted to send it even several days earlier :)
15:17:20 <kparal> the FIXMEs will be hopefully solved soon
15:17:31 <jlaska> anything they need help with?
15:17:51 <jlaska> sounds like they are 'aware' and wiki updates coming soon...
15:17:52 <kparal> I might help them to create LiveCDs
15:18:03 <kparal> apart from that they handle everything on their own
15:18:20 <jlaska> alright, thanks for keeping in touch with them
15:18:33 <jlaska> of course, give a holler if you need help creating/hosting images
15:18:45 <kparal> will do
15:18:52 * jlaska would like to have a positive contribution to hosting test day images this release :)
15:19:01 <jlaska> also to note ... this is our last scheduled test day
15:19:22 <jlaska> if anyone wants to schedule another event, please let us know (fedora-qa ticket or test@ mailing list)
15:19:57 <jlaska> which reminds me, there was a request for a dual-boot test day
15:20:10 <jlaska> I'll re-ping on that topic to see if that would make sense for F-15 (https://fedorahosted.org/fedora-qa/ticket/135)
15:20:16 <jlaska> #action jlaska - check-in on https://fedorahosted.org/fedora-qa/ticket/135
15:20:40 <jlaska> #topic AutoQA package acceptance update
15:20:51 <jlaska> kparal guide us through the autoqa wilderness please!
15:21:32 <kparal> ok, so, there were a few new patches in autoqa last week
15:21:53 <kparal> the email results should now contain a traceback in case the test case crashed
15:22:10 <kparal> we now catch errors even in setup() method
15:22:15 <jlaska> #info Email test results now include detailed traceback
15:22:31 <kparal> jlaska helped to update some documentation
15:22:47 <jlaska> kparal: there were 2 more outsanding docs tickets
15:22:53 <jlaska> I think I'd need some guidance on those
15:23:09 <kparal> and there will be more tickets soon, that's for sure :)
15:23:10 <jlaska> #link https://fedorahosted.org/autoqa/query?status=new&status=assigned&status=reopened&milestone=Outdated+documentation
15:23:25 <jlaska> kparal: heh, c'mon ... documentation is self-updating :P
15:23:29 <kparal> but now, we have a milestone for outdated documentation, an idea of jskladan
15:24:06 <kparal> wwoods: you're here now?
15:24:26 <kparal> wwoods: I don't want to post your updates, if you're really here :)
15:24:32 * jlaska suspects he's behind a steering wheel at the moment ... heading into the office at a high rate of speed
15:25:11 <kparal> ok, so wwoods posted a first blogpost of his highly desired 'depcheck series': http://qa-rockstar.livejournal.com/10187.html
15:25:26 <kparal> more to come, he says
15:25:28 <jlaska> maxamillion this topic is meant as a check-in for how AutoQA is progressing towards automating the package update acceptance plan (https://fedoraproject.org/wiki/QA:Package_Update_Acceptance_Test_Plan)
15:25:43 <jlaska> #link http://qa-rockstar.livejournal.com/10187.html
15:25:50 <jlaska> kparal: I just saw part#2 hit the planet a moment ago
15:25:57 <kparal> great!
15:26:04 <jlaska> #link http://qa-rockstar.livejournal.com/10368.html
15:26:04 <maxamillion> jlaska: ah! thanks :D
15:26:21 <kparal> the current plan is to make depcheck post karma comments to bodhi
15:26:33 <kparal> expect this in the following weeks
15:26:44 <maxamillion> oooo
15:26:47 <maxamillion> that'd be cool
15:26:52 <kparal> and jskladan has some more updates, let's hear him:
15:27:07 * jlaska imagines kparal handing the microphone off to jskladan
15:27:21 <jlaska> #info the current plan is to make depcheck post karma comments to bodhi
15:27:24 <jskladan> ok, so i've done some research on the turbogears2 front, and created simple proof-of-concept 'generic frontend' which can show results of testplans, if given metadata in proper format
15:27:29 * jskladan searching for the mail
15:27:39 <jlaska> jskladan: oooh, goodie!
15:28:04 <jskladan> this thread: https://fedorahosted.org/pipermail/autoqa-devel/2010-September/001187.html
15:28:25 <jskladan> so basically, you can specify a structure of the testplan like this: https://fedoraproject.org/wiki/User:Jskladan/Sandbox:Package_Update_Acceptance_Test_Plan_Metadata
15:28:58 <jskladan> and if resultsdb has the required data, it can show the results
15:29:13 <jskladan> (beware, this is ugly!) http://test1185.test.redhat.com:8080/?envr=openssh-5.4p1-3.fc13
15:29:23 <jlaska> jskladan: can you screenshot that?
15:29:32 <maxamillion> jskladan: that appears to be inside the firewall
15:29:39 <jlaska> jskladan: since not everyone can see on the .redhat.com network
15:29:43 <jskladan> gimme a moment :)
15:29:45 <maxamillion> jlaska: +1
15:31:05 <jlaska> while jskladan is screenshot'ing ... just to note something that didn't make sense to me initially, but jskladan cleared it up
15:31:32 <jskladan> http://jskladan.fedorapeople.org/ResultsDB%20Package%20Acceptance%20Test%20Plan.html
15:31:32 <jlaska> the wiki structure posted earlier (https://fedoraproject.org/wiki/User:Jskladan/Sandbox:Package_Update_Acceptance_Test_Plan_Metadata) allows anyone to define how autoqa test results will be grouped and organized for a particular test plan
15:31:46 <jlaska> jskladan: thanks!
15:32:16 <maxamillion> jskladan: ah, very cool
15:32:21 <jskladan> yes, so if you had an access to the internal site (shame on me), you could play around with that metadata
15:32:22 <jlaska> jskladan: that shows a lot of possibilities
15:32:53 * wwoods here, reading scrollback
15:33:00 <jlaska> wwoods: hey!
15:33:06 <maxamillion> jskladan: so ... question, where is the code that performs the test that produces that output? (or is that output generated off resultsdb?)
15:33:35 <jskladan> for example, if you'd remove the rpmlint from 'mandatory' group, it would  disappear from the frontend... same for the 'group results' etc.
15:33:57 <jskladan> maxamillion: not really sure about your question
15:34:18 <maxamillion> jskladan: did I word it badly? (I'm really good at that)
15:35:00 <jskladan> maxamillion: do you want to know "what creates the webpage" or "what provides the results shown on that page"?
15:35:31 <maxamillion> jskladan: what provides the results shown on that page?
15:35:41 <jskladan> the results will be stored in the resultsdb automagically right from the autoqa
15:35:48 <maxamillion> ah, ok
15:35:52 <maxamillion> good stuff :)
15:36:19 <jskladan> (the changes are in the jskladan branch of autqa git, mmnt)
15:36:44 <jskladan> http://git.fedorahosted.org/git/?p=autoqa.git;a=commit;h=46b4019b7608a7947bbda27c0219b67698985841
15:36:47 <jskladan> basically this
15:37:07 <jlaska> how do you guys want to handle that code?  Should we hold off until merging until after depcheck is completed?
15:37:11 <jlaska> or before?
15:37:14 <wwoods> maxamillion: so autoqa tests report to resultsdb, and then we have test plan metadata that says "show results for these tests: [...]"
15:37:27 <jskladan> wwoods: exactly
15:37:41 <wwoods> and an autoqa *frontend* will read that metadata, pull the appropriate results out of resultsdb, and show them to you
15:38:02 <jskladan> wwoods: maxamillion: and that ugly web page is supposed to be that frontend
15:38:18 <maxamillion> ah, ok
15:38:19 <jskladan> (will be nicer, though - i'm no web designer :-/)
15:38:20 <maxamillion> makes sense now
15:38:33 <wwoods> heh! yep - it'll be pretty later, but making it show the right data is the first goal
15:38:38 * jlaska pretty jazzed by the wiki metadata potential
15:38:50 <jskladan> wwoods: jlaska: thanks for helpimg me out with the description of this magic :)
15:39:00 <jlaska> jskladan: i'm still learning!
15:39:35 <jlaska> kparal: I'm behind on the thread, but there is also an active discussion around improving rpmlint?
15:40:08 <kparal> jlaska: there is so active discussion that right now there are 2 new messages even I haven't still read :)
15:40:47 <jlaska> kparal: the discussion is around a method to allow maintainers to whitelist/ignore specific rpmlint test results
15:40:49 <kparal> basically we're discussing possible ways how to store config file defining rpmlint output whitelist
15:40:50 <jlaska> ?
15:40:55 <jlaska> better phrased, thanks
15:41:18 <kparal> and I'm continuously learning from that discussion
15:41:41 <kparal> oh, 3 new messages
15:41:43 <jlaska> +1 :)
15:42:01 <jlaska> alright, what else on the autoqa front?
15:42:11 <wwoods> jskladan: heh no problem - the design is a little complicated (and pretty clever, I think) so we might want a blog post or two to explain it, someday soon
15:42:23 <jlaska> jskladan: feeling bloggy? :)
15:42:28 <kparal> jlaska: I think we have covered almost everything
15:42:37 <jlaska> kparal: okay ...
15:43:03 <jskladan> jlaska: not really :-D
15:43:13 <jlaska> oh, kparal, you mentioned you were planning to look into creating a depcheck wiki test case once wwoods posted all the depcheck blogs, anything else to add there?
15:43:29 <jskladan> jlaska: i can try to work something out, though
15:43:29 <jlaska> jskladan: it's tough to find the focus to crank those out
15:43:46 <kparal> jlaska: nothing right now
15:43:55 <jskladan> but i'll need some corrections an re-wordings from native speaker, heheh :)
15:43:56 <jlaska> wwoods: btw ... nice posts, very imformative
15:44:22 <jlaska> alright, thanks all ... moving on
15:44:42 <jlaska> I had a topic from last week on the list still ...
15:44:44 <jlaska> #topic F-14-NTH (Nice to have) proposal status
15:44:56 <jlaska> Not sure if there is anything new on this front
15:45:16 <jlaska> I suspect the wiki pages will move out of draft coming soon
15:45:25 <jlaska> not sure if adamw plans to complete this before or after release
15:45:53 <jlaska> stay tuned to the list for follow-up
15:46:04 <jlaska> alright, everyone's favorite topic ...
15:46:06 <jlaska> #topic Open discussion <your topic here>
15:46:09 <adamw> i was planning to do it friday
15:46:13 <adamw> ran out of time though
15:46:24 <jlaska> adamw: 4+ hour meetings will do that to your day
15:46:47 <adamw> heh
15:47:31 <jlaska> Meetbot is hungry and wants your <topics>
15:47:34 <jlaska> feed it
15:47:51 * jlaska makes sure he spelled meetbot, not meatbot
15:48:04 <jlaska> we'll close things out in 2 mins
15:48:10 <jlaska> tick tock tick tock ...
15:49:56 <jlaska> 10 seconds ...
15:50:03 <jlaska> 5 seconds ...
15:50:13 <jlaska> thanks all, have a great day
15:50:20 <jlaska> good luck with continued F-14-Final testing!
15:50:22 <jlaska> #endmeeting