12:00:31 <ndevos> #startmeeting
12:00:31 <zodbot> Meeting started Tue Mar 10 12:00:31 2015 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:31 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:00:37 <ndevos> #info Agenda: https://public.pad.fsfe.org/p/gluster-bug-triage
12:00:43 <ndevos> #topic Roll Call
12:00:56 * lalatenduM is here
12:01:04 * rafi here
12:01:04 <ndevos> hi lalatenduM!
12:01:10 <lalatenduM> hi ndevos
12:01:10 * ndevos _o/ rafi
12:01:20 <rafi> hi ndevos
12:01:40 <ndevos> anyone knows if atinmu, hchiramm or others will join?
12:01:50 * hchiramm in
12:01:57 <lalatenduM> ndevos, btw I have a meeting in few minutes , so I am mostly here to update status on my AIs
12:02:02 <ndevos> kkeithley has an excuse *again* :-/
12:02:11 <ndevos> lalatenduM: okay, thats fine
12:02:18 <lalatenduM> ndevos, whats the excuse this time :)
12:02:31 <ndevos> lalatenduM: dentist, I think?
12:02:52 <ndevos> well, lets get some stuff done
12:02:53 <lalatenduM> ahhh , he is eating lots of chocolates ;)
12:03:03 <ndevos> :)
12:03:05 <ndevos> #topic Last weeks action items
12:03:30 <ndevos> hmm, hagarth isnt there, and the majority are his...
12:03:42 <ndevos> #info subtopic: lalatenduM will send a reminder to the users- and devel- ML about (and how to) fixing Coverity defects
12:03:58 <lalatenduM> ndevos, http://build.gluster.org/job/Automated%20%20Covscan%20runs/
12:04:22 * ndevos looks
12:04:38 <lalatenduM> ndevos, once the periodic coverity runs starts running , we can send the mail
12:05:01 <lalatenduM> ndevos, the job is ready but it is failing bcz of a permission issue
12:05:15 <ndevos> lalatenduM: nice! and is that a scheduled Jenkins job?
12:05:17 <lalatenduM> so I need help of JustinClift or someone who has root access
12:05:20 <ndevos> (or will be?)
12:05:29 <lalatenduM> ndevos, yes it will run twice every week
12:05:54 <ndevos> lalatenduM: please send an email to the gluster-infra list with your request
12:06:01 <lalatenduM> ndevos, ok
12:06:35 <ndevos> lalatenduM: anything more to add?
12:06:37 <lalatenduM> can anyone take the ai to send the mail abt "send a reminder to the users- and devel- ML about (and how to) fixing Coverity defects"
12:07:01 <lalatenduM> ndevos, hchiramm ^^
12:07:09 <ndevos> #action lalatenduM 's automated Coverity setup in Jenkins need assistance from an admin with more permissions
12:08:03 <ndevos> lalatenduM: I guess we can, but I'm not really sure where/how to check the coverity report...
12:08:19 <lalatenduM> ndevos, ok lets take it to next meeting
12:08:31 <ndevos> okay
12:09:08 <ndevos> #agreed Try to find someone (not lalatenduM) to send the Coverity reminder/howto to the lists
12:09:23 <ndevos> #info subtopic lalatenduM initiate a discussion with the RH Gluster team to triage their own bugs when they report them
12:10:07 <lalatenduM> ndevos, I will consider it is done as of now :)
12:10:37 <lalatenduM> may be hagrath can do it in another level :)
12:10:44 <ndevos> lalatenduM: okay, I've seen some of the bugs they reported, and they added a special tracker, right?
12:10:56 <lalatenduM> ndevos, yes a tracking bug
12:11:22 <lalatenduM> ndevos, do you think the bugs were triaged by them?
12:11:32 <lalatenduM> if not we have to remind them again
12:11:35 <ndevos> I think we're good then, and if RH QE/dev people dont triage their own bugs, we'll talk to hagarth about it
12:12:09 <ndevos> #agreed RH QE/dev people should now know how to triage their own bugs, we'll talk to hagarth about it if they fail to do so
12:12:12 <lalatenduM> ndevos, yeah I think hagarth is the right person for this
12:12:38 <ndevos> #info subtopic: ndevos  will send an email to gluster-devel with some standard bugzilla  queries/links to encourage developers to take NEW+Triaged bugs
12:13:07 <ndevos> hmm, I started to put the link together (loooong ago), just did not send an email yet :-/
12:13:40 <ndevos> #info subtopic: lalatenduM will look into using nightly builds for automated testing, and will report issues/success to the mailinglist
12:13:53 <lalatenduM> ndevos, its in progress
12:14:02 <lalatenduM> Got in to a test harness issue
12:14:11 <lalatenduM> which is not resolved yet :(
12:14:17 <ndevos> yeah, I figured
12:14:48 <ndevos> lalatenduM: got a rough ETA?
12:15:36 <ndevos> lalatenduM: and would that be a job that could potentially use special debug rpms too? (like ./configure --enable-debug)?
12:15:37 <lalatenduM> ndevos, next week
12:16:02 <lalatenduM> ndevos, nope , we will be using the rpms from nightly builds
12:16:13 <lalatenduM> if required we can start glusterd with --debug
12:16:18 <lalatenduM> and run tests
12:16:27 <ndevos> lalatenduM: what if the nightly builds produce two sets of rpms?
12:16:51 <lalatenduM> ndevos, yes we can the debug RPMs too :)
12:16:57 <ndevos> "glusterd --debug" is different from "./configure --enable-debug", the 2nd is way more strict
12:17:13 <lalatenduM> ndevos, ahh I thought both are same
12:17:46 <ndevos> no, calls like GF_ASSERT() will not error out in standard builds, but will segfault on the --enable-debug ones
12:18:39 <ndevos> #action ndevos needs to look into building nightly debug rpms that can be used for testing
12:18:45 <lalatenduM> ndevos, yup
12:18:59 <lalatenduM> ndevos, I thought that hold true for glusterd --debug
12:19:04 <lalatenduM> holds*
12:19:15 <lalatenduM> I mean I will get core dumps for assert
12:19:19 <ndevos> lalatenduM: would two different repositories work best? or a glusterfs-debug-3... package?
12:19:51 <ndevos> lalatenduM: I'm not sure, but there is definitely a difference in the memory allocation/checking
12:20:22 <lalatenduM> ndevos, lets think about , I will get back on this
12:21:08 <ndevos> #action lalatenduM and ndevos need to think about and decide how to provide/use debug builds
12:21:52 <ndevos> any other items that we could discuss?
12:21:57 <hchiramm> lalatenduM, ndevos cant we provide debug rpms from a different repo ?
12:22:04 <hchiramm> debugrepo ?
12:22:08 <ndevos> hchiramm: yes, we could
12:22:10 <lalatenduM> hchiramm, yup, that can be done
12:22:29 <hchiramm> so that we can enable the repo if needed and pull those
12:22:42 <ndevos> hagarth: did you join to give a status update on your action items ( https://public.pad.fsfe.org/p/gluster-bug-triage )?
12:23:02 <ndevos> hchiramm: yeah, that is one option
12:23:12 <hchiramm> yep
12:23:34 <ndevos> I guess that would be the easiest, but lets think about that a little more
12:24:09 <ndevos> lalatenduM: oh, btw, do those tests include things like qemu-img commands with a gluster:// url?
12:24:30 * ndevos would be interested to have automatically test libgfapi
12:24:41 <lalatenduM> ndevos, nop :)
12:24:46 <lalatenduM> nope*
12:25:14 <ndevos> lalatenduM: oh, okay, that needs some work too then...
12:25:16 <lalatenduM> We should have a test for libgfapi
12:25:20 <lalatenduM> yup
12:25:40 <hagarth> ndevos: done
12:25:55 <ndevos> #action lalatenduM provide a simple step/walk-through on how to provide testcases for the nightly rpm tests
12:26:01 <ndevos> hagarth: thanks :)
12:26:36 <ndevos> #action ndevos to propose some test-cases for minimal libgfapi tests
12:26:49 <lalatenduM> ndevos, not sure if I can provide the testcases
12:27:11 <ndevos> lalatenduM: thats fine, as long as we as a community can add more cases
12:27:42 <lalatenduM> ndevos, ok lets discuss this offline
12:28:03 <ndevos> lalatenduM: ok
12:28:20 * ndevos is in the office, and the lights turn off every now and then...
12:28:43 <ndevos> #topic Group Triage
12:29:11 <ndevos> 10 new bugs - http://goo.gl/0IqF2q
12:29:35 <ndevos> rafi, atinmu: wake up, this is your favorite part!
12:29:47 <ndevos> lalatenduM: I guess you're leaving us now?
12:29:49 * hchiramm locks 1199075
12:29:51 * lalatenduM locks 1199906
12:30:05 <lalatenduM> the 1st and last bug to triage for today :)
12:30:12 * ndevos locks 1200255
12:30:36 * rafi locks 1199436
12:32:03 * ndevos 1200150
12:34:08 * hchiramm "Do we need to triage tracker bug ? :)
12:37:21 * hchiramm locks 1198810
12:38:10 <ndevos> hchiramm: just move trackers to assinged or something, assign it to whoever takes care of the feature
12:38:27 <hchiramm> ndevos, ok..
12:40:05 * hchiramm locks 1199352
12:40:31 * hchiramm locks 1198573
12:40:37 * rafi locks 1198746
12:43:23 * ndevos locks 1200372
12:45:43 * ndevos 1198614
12:49:32 * ndevos 1198746
12:50:23 <ndevos> #topic Open Floor
12:50:41 <ndevos> hchiramm, lalatenduM, rafi, atinmu: got any other topics?
12:51:02 <rafi> ndevos: nop :)
12:51:25 <hchiramm> no from me :)_
12:51:42 <ndevos> okay, I guess thats it for today then :)
12:51:47 <ndevos> thanks hchiramm, lalatenduM, rafi, atinmu and hagarth!
12:51:51 <hchiramm> bye,. thanks :)
12:51:52 <ndevos> #endmeeting