12:12:05 #startmeeting gluster bug triage meeting 12:12:05 Meeting started Tue Apr 12 12:12:05 2016 UTC. The chair is rafi. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:12:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:12:05 The meeting name has been set to 'gluster_bug_triage_meeting' 12:12:18 #info agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 12:12:26 #topic Roll call 12:12:51 * hgowtham \0_ 12:13:01 * skoduri is here 12:13:02 o/ 12:13:10 o/ 12:13:12 * kkeithley_ is here 12:13:41 * ndevos _o/ 12:14:07 i think we have good number folks here 12:14:15 moving to next topic 12:14:40 #topic action items from last meeting 12:15:08 #topic msvbhat will look into lalatenduM's automated Coverity setup in Jenkins which need assistance from an admin with more permissions 12:15:33 I think msvbhat is not around 12:15:46 so moving this item to next meeting 12:15:57 #action msvbhat will look into lalatenduM's automated Coverity setup in Jenkins which need assistance from an admin with more permissions 12:16:11 #topic ndevos need to decide on how to provide/use debug builds 12:16:26 ndevos: your turn 12:16:31 yes, still need to do that 12:16:50 ndevos: no worries 12:17:04 ndevos: will carry forward to next meeting 12:17:10 ndevos: or do you need more time 12:17:24 put it for next meeting again 12:17:43 I need to do it, just do not know when I have the time for it 12:17:51 and a reminder helps :) 12:17:53 #action ndevos need to decide on how to provide/use debug builds 12:17:55 ndevos: np 12:18:14 #topic Manikandan and gem will update on bug automation 12:18:30 Manikandan: gem : any updates on this ? 12:19:02 rafi, i think Manikandan is held up with another meeting 12:19:28 hgowtham: oh oh 12:19:39 :) 12:19:58 I remember gem mentioning about pushing some initial script to our repo 12:20:13 Do we have any update on that ? 12:20:19 ndevos: are you aware of any ? 12:20:36 rafi, hey! 12:20:43 rafi, we haven't tested the code yet 12:20:59 rafi, If we could get access to test it, that would be better 12:21:21 gem: you mean access to our infra ? 12:21:24 gem: have you been in tough with kshlm about that? 12:21:51 ndevos, Manikandan was getting in touch with kshlm regarding this 12:21:55 rafi: I think this is for the scripts that need to run as Gerrit hooks 12:22:13 (so, in the Gerrit process/service itself) 12:22:18 ndevos: okey 12:22:42 gem: ok, could you convince Manikandan to send a request on gluster-infra about it? 12:23:00 ndevos, okay 12:23:09 ndevos: i will put an action item ;) 12:23:39 rafi: sure, lets see if gem and Manikandan have something to report next week ;-) 12:23:44 #action Manikandan to followup with kashlm to get access to gluster-infra 12:24:40 ndevos: they are doing good job, everyone will get the fruits of their job sooner :) 12:25:03 * rafi is eagerly looking for automated bug status 12:25:10 rafi: yes, it would be a great thing to have! 12:25:38 coool 12:25:49 moving into next topic 12:25:56 gem: for many things, we could even have a Jenkins job do the work, and not rely on Gerrit too much, I think? 12:26:15 gem: thanks for updating 12:26:21 #topic msvbhat provide a simple step/walk-through on how to provide testcases for the nightly rpm tests 12:26:39 automatically moving to next meeting as msvnhat is not present 12:26:44 ndevos, yes. we could use jenkins APIs in a lot of places 12:26:44 #action msvbhat provide a simple step/walk-through on how to provide testcases for the nightly rpm tests 12:27:06 #action ndevos to propose some test-cases for minimal libgfapi test 12:27:22 yes, need to do that too... stil 12:27:23 l 12:27:36 ndevos: okey 12:27:46 ndevos: I will propose for next week 12:28:00 #action ndevos to propose some test-cases for minimal libgfapi test 12:28:23 great, we are done with action items from last meeting 12:28:33 here we start the main agenda 12:28:59 #topic Group triage 12:28:59 we have 7 bugs to traige 12:29:21 #info you can fine the bugs to triage here in https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:29:25 #link https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:29:55 hgowtham: skoduri post-factum jiffin kkeithley_ ndevos gem : let'us start grooup triage 12:30:07 yes lloking at it 12:30:11 *looking 12:34:07 just to point out, there are a lot of bugs in ndevos' bugs with incorrect status report that are assigned to nobody, but have patches posted or merged. There are too many for one person (e.g. me) to fix them all. Maybe in a future meeting we could address those. 12:34:27 start to address those 12:36:35 kkeithley_: that gives me an idea! 12:36:48 we can complain about incorrect assignees too :) 12:38:21 #halp extend check-bugs.py to complain about bugs assigned to nobody or bugs@gluster.org but do have patces 12:38:25 #link https://github.com/gluster/release-tools/blob/master/check-bugs.py 12:40:05 #link http://www.gluster.org/pipermail/gluster-devel/2016-April/049043.html 12:40:41 gem: for your automation scripts, do you use check-bugs.py or something similar too? 12:41:04 it could easily be extended to get a bz# as parameter and only check that 12:41:38 ndevos: I see a needinfo from you on https://bugzilla.redhat.com/show_bug.cgi?id=1323895 , 12:41:39 Bug 1323895: low, unspecified, ---, bugs, NEW , Can I configure data transfer network and ping check network separately? 12:41:49 ndevos: i think we can skip this fro now, right ? 12:41:54 *for now 12:42:25 rafi: yeah, but maybe someone should ping Du about it? 12:42:33 * ndevos always wonders if he is on irc 12:42:52 ndevos: his nink name is raghug 12:43:15 ndevos: I will followup on this 12:43:16 ah, right, raghu vs raghug and both are called Raghavendra 12:43:25 ndevos: ya :D 12:43:32 ndevos, we are not using that check-bugs.py. We were writing whole implementation from scratch. 12:43:37 * ndevos probably never learns 12:43:46 #action rafi needs to followup on #bug 1323895 12:43:47 Bug https://bugzilla.redhat.com:443/show_bug.cgi?id=1323895 low, unspecified, ---, bugs, NEW , Can I configure data transfer network and ping check network separately? 12:44:02 * gem thinks she should look into it now that she knows about it 12:44:26 gem: ok, well whenever you post your code, we might be able to merge some pieces :) 12:44:51 gem: hmm, and maybe it's doing the inverse from what you are doing.... 12:45:28 ndevos, yes :) 12:45:54 I think we are done with group triage 12:46:00 moving to next topic 12:46:21 #Topic Open Floor 12:46:42 please feel free to bring your ideas or concerns 12:46:43 bugs with incorrect status report that are assigned to nobody, but have patches posted or merged 12:47:12 * kkeithley_ enjoys repeating himself. ;-) 12:48:05 kkeithley_: that's good 12:48:40 so we can start to address those next time? 12:48:42 i think we can include bugs with incorrect status in bug triage 12:49:01 I would like to hear from everyone 12:49:05 kkeithley_: you say "nobody", do you mean "bugs_at_gluster.org"? 12:49:27 ndevos: jiffin skoduri hgowtham post-factum gem : ^ 12:50:04 well, we could actually script that... 12:50:04 yes sure :) 12:50:30 ndevos: script to get the incorrect bugs ? 12:50:43 ndevos: or automatic healing ? 12:50:51 ndevos: :) 12:51:08 rafi: the script to get the incorrect bugs is called check-bugs.py, see ^^^ 12:51:17 ndevos: ya 12:51:36 rafi: the "bug healing" could be "assign the person posting the patch to the bug" 12:52:55 ndevos: okey , should we do that now ? or wait for much enhanced automatic bug status update 12:53:39 rafi: the status update that gem and Manikandan work on will only be effective for bugs that get new patches posted/updated 12:53:57 ndevos: ya, I was about to ask 12:54:15 rafi: adding it as a task for next weeks meeting would probably be good 12:54:40 ndevos: yes, nobody = bugs at gluster dot org 12:56:08 ndevos: I'm not good at scripting. please forgive me if this is a stupid question ? is it difficult to read from the older commands and update the assignee ? 12:57:01 rafi: it's easy, there is a bugzilla command (install the python-bugzilla package) 12:57:21 ndevos: okey 12:57:31 bugzilla modify --assignee=someone@example.com 123456 12:57:55 okey 12:58:01 or, something like that anyway 12:58:13 ndevos: okey 12:58:25 ndevos: we can discuss this in next meeting 12:58:28 it's more tricky to get the email of the author from the git commit 12:58:38 ndevos: we almost there to end the meeting 12:59:08 /we have 1 mnt left to finish the meeting :) 12:59:17 well, it's not tricky, I just dont know the syntax immediately: git show --format=%email $commit 12:59:45 but that needs a mapping of the gerrit change-id to commits... hmm 13:00:12 #action need to discuss about writing a script to update bug assignee from gerrit patch 13:00:12 * ndevos just rambles on if the moderator does not intervene 13:00:50 ndevos: np 13:01:09 ndevos: I will take that up, so that I can study that 13:01:40 does any one have anything to brig for today ? 13:01:58 coool 13:01:58 rafi: cool, thanke 13:02:32 I guess all of us are exhausted :D 13:02:38 letus stop the meeting] 13:02:46 #endmeeting