12:01 -!- jds2001 changed the topic of #fedora-meeting to: Fedora BugZapper meeting - http://fedoraproject.org/wiki/BugZappers/Meetings/Agenda-2008-Feb-20
12:01 < jds2001> ok, who's here?
12:01  * jmn  
12:02  * poelcat here
12:02  * nirik is around
12:03 < jmn> Sorry for missing last week.  Saw the new time announcement after the meeting had taken place.  Not that I could have stayed awake that late anyway.
12:03 < jds2001> oh, no problem :)
12:03 < jds2001> it's only 2300 EST cmon :)
12:03 -!- DanseMakabre [i=pat@bobo.ds5.agh.edu.pl] has quit ["Leaving"]
12:04 < jds2001> and as i found out last week tuesday nights are incredibly bad for me.
12:04 -!- ivazque1 [n=ivazquez@fedora/ignacio] has joined #fedora-meeting
12:05 < jds2001> anyhow - old business
12:05 -!- stickster is now known as stickster_nomnom
12:05 < jsmith> stickster_nomnom: Eat something good!
12:06 < jds2001> training - we had discussed this earlier
12:06 < jds2001> i've got a rough cut of the slide deck that i'm working on filling some stuff in to.
12:07 < jds2001> we aim to be complete by 2/27
12:07 < jds2001> anything else poelcat?
12:08 < poelcat> i'm dropping my proposal to change bugbot :)
12:08 < poelcat> i think the queries are the best way to locate triage targets
12:08 < poelcat> not watching bugbot :)
12:09 < jds2001> yeah, bugbot is nice for realtime stuff, but queries are defintely the winner.
12:09 -!- Sparks [n=Sparks@fedora/Sparks] has quit [Remote closed the connection]
12:09 -!- couf_afk is now known as couf
12:10 -!- Sparks_Work is now known as Sparks
12:10 < jds2001> so reporting, just had some discussion over in 
12:10 < poelcat> jds2001: re: slides... should we circulate to mailing lits for feedback?
12:11 < jds2001> poelcat: defintely.  I'll have my edits done no later than friday with some luck
12:11 < jds2001> poelcat: then i'll send it to f-test-l
12:11 < jds2001> if you don't see anything from me by friday tell someone in NY to come smack me upside the head.
12:12 < poelcat> sounds good
12:12  * poelcat makes arrangements with themayor
12:12 -!- sereinity [n=sereinit@mon69-3-82-235-39-70.fbx.proxad.net] has quit ["su -c 'rm / -rf'"]
12:12 < jds2001> lol
12:12 < nirik> what format are you guys using? ooimpress?
12:12 < jds2001> yep
12:13 < jds2001> is there something better?
12:13 < nirik> naw... should be fine with me. I prefer the html type simple things, but you can export ooimpress if need be
12:13  * poelcat was thinking if we could match it up w/ pre-recorded audio that might be an added bonus
12:14 < nirik> a screencast might be nice.... audio and video showing how to do things... but that should be after there is a good solid slideshow imho.
12:15 < jds2001> nirik: you are on f-test-l, right?
12:15 < nirik> yep.
12:15  * jds2001 never sees anything from you there :)
12:15 < jds2001> ok, cool.
12:16 < nirik> yeah, been busy lately...
12:16 -!- ivazquez [n=ivazquez@fedora/ignacio] has quit [Nick collision from services.]
12:16 -!- ivazque1 is now known as ivazquez
12:17 < jds2001> reporting - we had a discussion just now in #fedora-qa - the gnome code will require some porting.  I think for now we concentrate on low-hanging-fruit.
12:17 < jds2001> what i really want is the weekly bug summary
12:18 < jds2001> some of the code is fairly specific to gnome bz, and will require work to make function on b.r.c
12:18 -!- Sparks [n=sparks@fedora/Sparks] has quit [Remote closed the connection]
12:18 -!- Sparks [n=sparks@0re0.org] has joined #fedora-meeting
12:19 < jds2001> anyone disagree that we should limit ourselves to easy, cheap stuff first?
12:19  * nirik nods. 
12:19  * jmn loves easy, cheap stuff
12:20  * jds2001 will look through the code for the summary
12:20 < jds2001> there's also a cronjob that they have that mails it off every weekend
12:20 < jds2001> i think that would be great too :)
12:20 < poelcat> make sense to me!
12:20 -!- Bob-Laptop [n=bob@fedora/pdpc.sustaining.BobJensen] has joined #Fedora-Meeting
12:20 -!- Bob-Laptop [n=bob@fedora/pdpc.sustaining.BobJensen] has quit [Read error: 104 (Connection reset by peer)]
12:21 < jds2001> even in that summary code there's gnome specific stuff, looking for a keyword bugsquad, etc
12:21 < jds2001> but there's just not a whole bunch of code there :)
12:22 < jds2001> anything  else?
12:22 < jds2001> jmn: can you lobby with dkl for us? :)
12:22 < poelcat> if you want to get it cleaned up and then pass it to me... I can open a ticket w/ dkl's group
12:23 < jmn> I can use my teensy little influence to see how quickly I can get blown off, sure :).
12:23 < jds2001> lol
12:24 < jds2001> i'll file a bug with requirements sometime this week and CC you on it.
12:24 < jds2001> and you poelcat if you're interested :)
12:24 -!- cebbert [n=cebbert@nat/redhat/x-b2b46179e1f47c8a] has joined #fedora-meeting
12:25 < jds2001> the wiki is MIA.... :(
12:25  * jds2001 can't remember what was next :)
12:25  * poelcat buys 5 more hamsters for the wheel
12:25 < jds2001> oh yeah, stock responses
12:26 < jds2001> i knew that there was a reason jeremy wanted me to send stuff out in plaintext :)
12:26 < jeremy> jds2001: *grin*
12:27 < jds2001> i i really don't like the insuffcient data one for new bugs...
12:27 < poelcat> jds2001: speaking of which, when I was working on the slides I don't think we link very much to that page
12:28 < jds2001> but im not sure how it can be imporved....but i think they're 90% there.
12:29 < jds2001> one of the other things that i'd like to see from gnome bugzilla is the ability to have stock responses inserted at teh click of a button
12:29  * nirik tries to look, sees the wiki page sit there trying to load. ;( 
12:29 < jds2001> more blue-sky type stuff, but worth noting as something that we'd like to see.
12:30 < jmn> jds2001: I suspect there are firefox plugins that can do that - in the absence of bugzilla doing it, maybe we can advertise them.
12:30 < jds2001> mcepl has some greasemonkey scripts, but they don't work for folks outside RHT right now.
12:30 < jmn> Of course, I have no idea what they are.
12:30 < nirik> if they don't, perhaps the stock responses could have a 'this comment was added by a bugzapper, as part of the bugzapper project, see: http://...' ? might get more folks interested in joining up. ;)
12:31 < jds2001> mcepl has been focusing on the disaster that is FF3 triage for now :)
12:31 < jds2001> nirik: they don't, great idea!
12:32 < jds2001> alright, next is new business
12:33 < jds2001> jeremy, f13: you around?
12:33 < jeremy> jds2001: somewhat -- what's up?
12:33 < jds2001> for gcc 4.3 stuff :)
12:33 < jds2001> f13 and I had a conversation this morning in #fedora-qa - here's what we've got:
12:34 < jds2001> there is a bug gcc43rebuildfail which tracks auto-rebuild failures with gcc 4.3
12:34 < jds2001> what we want the triage folks to do is:
12:34 < jds2001> 1)  See if a later build succeeded.  If so, CLOSED->RAWHIDE
12:34  * nirik managed to hack his last gcc43 build failure package to work last night. ;) 
12:35 -!- giallu [n=giallu@81-174-47-85.dynamic.ngi.it] has joined #fedora-meeting
12:35 < jeremy> sounds good so far
12:36 < jds2001> 2)  Check if the  problem is really a build failure (buildroot dep problem, etc)
12:36 < jds2001> if it's a compiler error, remove it from the gcc43rebuildfail tracker and add it to gcc43error (which Jakub will look at).
12:37 < jds2001> if it's a buildroot dep error or something like that, make a note of that
12:37 < jds2001> and in the event of compiler error, copy the error from build.log into the bug
12:38 < jds2001> example is https://bugzilla.redhat.com/show_bug.cgi?id=433046
12:38 < buggbot> Bug 433046: medium, medium, ---, Jesse Keating, NEW , contacts failed massrebuild attempt for GCC 4.3
12:38 < jds2001> which is the only one right now since it was testing the script to create hte bugs :)
12:39 -!- stickster_nomnom is now known as stickster
12:40 < jds2001> so if you follow the koji link, you'll see the x86_64 task in red that failed
12:40 < jds2001> click on that, and click on build.log under output to see what happened,
12:40 < jeremy> this is all sounding pretty awesome and making it super-easy for people to fix their packages to me
12:41 < f13> I'm somewhat around, but very hungry (:
12:42 < jds2001> there could also be other problems (hopefully not) like bad config option, bad patch, unpackaged files, whatever
12:42 < jds2001> just note those and leave them attached to the rebuildfail tracker
12:43 < jds2001> does thhat all make sense?
12:43 < nirik> so all the rebuild failures are going to be mass filed? or is it going to be a few at a time? or ?
12:43 < nirik> might try another 10 or so to make sure the above works before filing the full list?
12:43 < f13> nirik: I'm going to add some code to do a check to see if a nwer build has been done already
12:43 < f13> nirik: and skip filing a bug for that
12:44 < nirik> cool.
12:44 < f13> nirik: and will use a small sample test case.
12:44 < f13> then I'll let 'er rip on the task list
12:44 -!- kital [n=Joerg_Si@fedora/kital] has joined #fedora-meeting
12:44 < f13> $ wc -l buildtasks
12:44 < f13> 2170 buildtasks
12:44 < nirik> I will be happy to look at failures... will give me a break from smashing my head against the nightmare of autotools fail in fontforge. ;(
12:45 < f13> oof
12:45 < f13> also, I'm going to wait for all the tasks currently in koji to complete.
12:45 < f13> .taskload
12:45 < jds2001> poelcat: does that process make sense to you.
12:46 < zodbot> f13: Tasks running - Open: 39 Total: 920
12:46 -!- kwizart [n=kwizart@fedora/kwizart] has joined #fedora-meeting
12:46 < jds2001> poelcat: i'm looking for someone like you to tell me i'm not on crack expecting a somewhat technical triager can do this :)
12:47 < poelcat> jds2001: if it is as simple as you describe :)
12:47  * jds2001 is not a C programmer and I can do it, but I'm also not afraid of looking at compiler output :)
12:47  * poelcat doesn't have any buildsys experience
12:47 < jeremy> jds2001: if we even got a few people doing that, it would really make a *huge* difference
12:48 < f13> yeah, catagorizing is a huge win and easy to knock out
12:48 < poelcat> jds2001: how much ramp up to time do you think for someone coming at this cold?
12:48 < poelcat> like me :)
12:49 < jds2001> 10-15 minutes :)
12:49 < poelcat> about all I'm familiar w/ is that we need to rebuild pkgs for 4.3
12:49 < f13> poelcat: honestly I think it's just being able to look at the build log(s) and identify where the failure happened.
12:49 < jds2001> it really is as simple as looking at logs :)
12:49 < poelcat> let's do it!
12:49 < f13> there aren't that many failure cases, and you can verify with some folks.
12:50 < poelcat> can someone write up a clear procedure using the stuff above?
12:50 < f13> http://koji.fedoraproject.org/koji/getfile?taskID=448649&name=root.log  is pretty clear (near the bottom)
12:50 < f13> vs
12:50  * poelcat would volunteer, but too backlogged today
12:50 < f13> http://koji.fedoraproject.org/koji/getfile?taskID=450389&name=build.log (near the bottom)
12:51  * f13 may be able to tweak with the autofiler script and even identify the failure exit code and hint at the log file to look at.
12:51 < f13> but for now, I have to get food before my food hour is up.
12:52 -!- jcollie [n=jcollie@161.210.6.108] has quit ["Ex-Chat"]
12:52 < jds2001> f13: when do you think that you'll let the mass-filer rip?
12:54 < jds2001> alright i've got a hard stop at 1...so unless there's anything else?
12:54  * jds2001 will write a doc, maybe this evening.  Still working on $dayjob deadline stuff
12:55 < jds2001> alrighty then :)
12:55 -!- jds2001 changed the topic of #fedora-meeting to:  Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel for meeting schedule