12:01:13 #startmeeting 12:01:13 Meeting started Tue Apr 28 12:01:13 2015 UTC. The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:28 #info Agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 12:01:33 #topic Roll Call 12:01:34 * kkeithley_ is here 12:02:07 * hchiramm is here 12:02:21 Hi ndevos and kkeithley_ 12:02:23 atinmu, kshlm, jiffin: attending? 12:02:32 #chair hchiramm kkeithley_ 12:02:32 Current chairs: hchiramm kkeithley_ ndevos 12:02:38 rafi1, ^^^ 12:02:42 is it namaskaramu in Malaylam? 12:02:54 namaskaram :) 12:03:05 and malayalam :) 12:03:06 Malayalam 12:03:08 * jiffin is here 12:03:28 #topic Status of last weeks action items 12:03:29 kkeithley_, now u can learn more words :) 12:03:38 yup 12:03:43 kkeithley++ 12:04:04 hagarth: any update on the nightly automated tests? did you send the email? 12:04:04 and hchiramm can teach more words :) 12:04:14 jiffin, yeah, without doubt 12:04:36 ndevos: nightly automated tests? I sent an email on automated builds for releases 12:04:58 hagarth: "hagarth start/sync email on regular (nightly) automated tests" is on the action items 12:05:19 * ndevos does not know who added that, or since when its on there 12:05:31 ndevos: ok, I'll do that by next week. I get some context now :). 12:05:43 hagarth: okay, thanks! 12:06:03 hagarth: how about "hagarth should update the MAINTAINERS file, add current maintainers and new components like Snapshot and other new features" ? 12:06:16 ndevos: I plan to do that later .. not immediately 12:06:30 hagarth: ok, we'll check next week again ;_ 12:06:33 ;) 12:06:49 ndevos: you can keep this stock answer for next week too 12:06:51 ndevos, this is bug traiging meeting 12:07:06 none of the other items have been acted on, so we'll move on then 12:07:06 lets move these actions to community meeting :) 12:07:16 hchiramm: yes, and those topics are on the agenda :) 12:07:22 #topic Group Triage 12:07:27 yes.. :) a suggestion 12:08:08 no bugs waiting on bugs@gluster.org 12:08:18 something wrong ? :) 12:08:20 #info 27 bugs to triage 12:08:30 http://goo.gl/WuDQun is the url for today 12:08:59 please take an irc lock when you open a bug for triaging 12:09:10 * hchiramm locks 1215022 12:09:21 * ndevos 1215421 12:09:24 1214649 12:09:33 * jiffin locks 1214629 12:10:15 * ndevos locks 1215420 12:10:39 * hchiramm locks 1215022 12:10:51 * hchiramm locks 1215017 12:11:11 1215149 12:11:24 1215419 12:11:53 1215017 12:12:03 * soumya lock 1215787 12:12:13 * jiffin locks 1215018 12:12:16 welcome soumya :) 12:12:25 hchiramm, :) 12:12:49 * ndevos 1215173 12:12:54 1215129 12:12:55 1215120 12:13:35 welcome Jose :) 12:13:48 1214677 12:14:00 1215129 12:14:12 * ndevos 1214563 12:14:35 ah.. conflict with kkeithley_ :) 12:14:57 oh, which one? 12:15:00 sorry 12:15:05 1215129 12:15:08 no worries.. 12:15:31 I didnt look the list properly 12:15:31 it was my mistake 12:15:51 1214671 12:15:59 1214822 12:16:13 1214662 12:16:50 1215664 12:17:09 1215033 12:17:26 1215033 12:17:29 hey! 12:17:49 * ndevos takes 1215025 instead 12:18:05 sorry 12:18:21 1215668 12:20:54 1215114 12:22:02 1215515 12:22:27 who is maintaining disperse? 12:22:38 (it's not in the MAINTAINERS file) 12:22:50 pranith, xavi? 12:22:51 xavi ? 12:23:05 xavih, ^^^ 12:23:15 yeah, apparently xavih is not very responsive. 12:23:22 pranith it is 12:23:33 1214912 12:24:20 1214994 12:24:24 1214169 12:25:17 soumya has the last bug, we're all done then 12:26:21 thanks :) 12:27:45 #info If you like to triage more bugs, please check https://public.pad.fsfe.org/p/gluster-bug-triage for links to older bugs and other components 12:28:01 #topic Open Floor 12:28:14 anyone wants to add a topic now? 12:28:45 ndevos, no from me 12:28:49 oh, http://bugs.cloud.gluster.org/ has components too, Aravinda send a patch for that, please have a look 12:29:25 https://github.com/gluster/gluster-bugs-webui/issues contains some more ideas on what to add, please add your RFE's there too 12:29:26 not bug triage, but "bug" related. release-3.7 has been added to the static analysis runs. Ripe territory for bugs to fix there 12:30:04 kkeithley++ thanks 12:30:05 http://download.gluster.org/pub/gluster/glusterfs/static-analysis/ 12:30:09 kkeithley_: is there a way to compare release-3.7 with the master branch issues you find? 12:30:24 well, "you"... 12:31:01 I suppose the outputs could be diffed... Not sure how easy or hard that would be to use 12:31:11 also we were discussing about nice renderging of the static analysis result 12:31:19 renderging/rendering 12:31:44 do we have any volunteer to work on it ? 12:32:33 * ndevos does not see anyone raising hands... 12:33:11 Coverity runs have HTML, but that's not much more than a "pretty print" of the text output. In a perfect world we would use the workbench and people could update with false positives so the same things don't keep getting reported over and over. 12:33:43 the html rendering is pretty good I believe 12:33:44 Maybe something for an intern to work on? We're getting a couple in Westford soon 12:33:47 kkeithley_: I think people do update the coverity project page 12:34:02 ah, and I noticed that there are some newly reported issues in nfs :-/ 12:34:27 kkeithley_, oh .. ok 12:34:28 yes, that's our official coverity project page. The coverity runs in static analysis aren't tied to that. 12:35:48 kkeithley_, do we need to keep previous run results in download.gl.org ? 12:35:59 http://download.gluster.org/pub/gluster/glusterfs/static-analysis/release-3.7/glusterfs-coverity/ 12:36:23 Is it fine to keep the last one ? 12:36:24 well, no, but how could that be sanely done? do both systems not report (at least partially) the same issues? 12:36:52 IIRC I have a cron job that deletes old results 12:37:03 I should check and make sure that's working correctly 12:37:14 for ex:http://download.gluster.org/pub/gluster/glusterfs/static-analysis/release-3.6/glusterfs-coverity/ 12:37:28 kkeithley_, ok.. thanks 12:37:35 kkeithley_: oh, *IDEA* ! Could we not have an intern look into getting elastic search to index these analysis results? 12:38:04 that could give some amazing graphs, and we can show how elastic search can use a gluster backend :D 12:38:30 sounds like a good idea 12:39:05 results over time would be awesome 12:39:15 yep :) 12:39:20 and, results of Jenkins test failures too! 12:39:24 ndevos, sorry I was away :( 12:40:00 atinmu: you missed all the fun, but there are still old bugs that we should triage at one point, you can do your share ;-) 12:40:12 atinmu: any open floor topic from you? 12:41:02 * ndevos guesses "no" 12:41:05 ndevos, no 12:41:09 :) 12:41:22 that all for today then, thanks all for joining! 12:41:27 #endmeeting