Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2015-02-03

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:34 shyam joined #gluster-dev
02:41 _Bryan_ joined #gluster-dev
03:42 anrao joined #gluster-dev
03:43 itisravi joined #gluster-dev
03:45 kshlm joined #gluster-dev
03:45 bala joined #gluster-dev
04:07 spandit joined #gluster-dev
04:09 atinmu joined #gluster-dev
04:11 shubhendu joined #gluster-dev
04:13 jobewan joined #gluster-dev
04:15 kshlm joined #gluster-dev
04:18 sakshi joined #gluster-dev
04:20 bala joined #gluster-dev
04:36 jiffin joined #gluster-dev
04:39 rafi joined #gluster-dev
04:48 anoopcs joined #gluster-dev
04:50 rjoseph joined #gluster-dev
04:54 ndarshan joined #gluster-dev
05:01 mikedep333 joined #gluster-dev
05:08 ppai joined #gluster-dev
05:22 anrao joined #gluster-dev
05:26 gem joined #gluster-dev
05:35 prasanth_ joined #gluster-dev
05:36 nkhare joined #gluster-dev
05:37 Manikandan joined #gluster-dev
05:38 FrankLu joined #gluster-dev
05:46 anrao joined #gluster-dev
05:47 overclk joined #gluster-dev
05:48 kdhananjay joined #gluster-dev
05:57 vikumar joined #gluster-dev
05:57 jiffin joined #gluster-dev
05:58 pranithk joined #gluster-dev
05:59 soumya__ joined #gluster-dev
06:14 raghu joined #gluster-dev
06:46 atinmu joined #gluster-dev
06:58 pranithk joined #gluster-dev
06:59 soumya__ joined #gluster-dev
07:21 pranithk joined #gluster-dev
07:25 atinmu joined #gluster-dev
07:27 vikumar joined #gluster-dev
08:04 kkeithley1 joined #gluster-dev
08:09 lalatenduM joined #gluster-dev
08:18 tdasilva joined #gluster-dev
08:27 hagarth joined #gluster-dev
08:59 kdhananjay joined #gluster-dev
09:16 shubhendu joined #gluster-dev
09:18 ndarshan joined #gluster-dev
09:48 atinmu joined #gluster-dev
09:57 kdhananjay joined #gluster-dev
10:12 ndarshan joined #gluster-dev
10:23 Manikandan joined #gluster-dev
10:34 shubhendu_ joined #gluster-dev
10:41 rafi joined #gluster-dev
10:44 rafi1 joined #gluster-dev
10:47 soumya joined #gluster-dev
10:59 atinmu joined #gluster-dev
11:16 soumya joined #gluster-dev
11:20 vikumar joined #gluster-dev
11:22 vikumar joined #gluster-dev
11:36 overclk joined #gluster-dev
12:04 overclk joined #gluster-dev
12:04 pranithk left #gluster-dev
12:05 itisravi joined #gluster-dev
12:11 jdarcy joined #gluster-dev
12:13 lalatenduM gem, hii
12:13 gem lalatenduM, hey..
12:13 gem lalatenduM, I have sent in the patch for integrating travis( http://review.gluster.org/#/c/9566/ ).
12:13 lalatenduM gem, cool
12:13 lalatenduM gem++
12:13 glusterbot lalatenduM: gem's karma is now 7
12:13 gem lalatenduM, disabled travis build, but.
12:13 lalatenduM gem, checking
12:13 gem lalatenduM, since jenkins take care of this, do we need that?
12:17 lalatenduM gem, did not get you , you mean we can use Jenkins in place of travis ?
12:18 gem lalatenduM, no no.. so main purpose of travis here is to automate coverity scan builds, right?
12:18 lalatenduM gem, yes
12:19 gem lalatenduM, along with this travis automatically runs all the regression tests, but is that really necessary?
12:19 gem lalatenduM, gluster build system does that already, right?
12:19 lalatenduM gem, nope, we not need travis to run regression tests
12:19 lalatenduM s/not/do not/
12:20 lalatenduM we have jenkins to run regression tests
12:20 gem lalatenduM, okay.. doubt cleared. the yml I pushed will work that way. :)
12:20 lalatenduM and regression tests run on different os distributions
12:20 lalatenduM e.g. fedora, free bsd, centos etc etc
12:21 lalatenduM gem, I have a review comment
12:21 gem lalatenduM, checking..
12:22 lalatenduM gem, pushed the comment now
12:22 hchiramm lalatenduM, I have my thought on it
12:23 lalatenduM hchiramm, ok, I am listening:)
12:23 hchiramm replied in gerrit review .
12:24 hchiramm our aim was to send the coverity result to gluster-devel  . Is nt it ?
12:29 lalatenduM hchiramm, yes, gem what is the purpose of notification_emai?
12:30 gem lalatenduM, hchiramm to notify gluster-devel after each cov_scan, we can add the mailing list id in coverity scan settings page itself..
12:30 gem lalatenduM, I was mistaken about the notification_email. hchiramm just cleared
12:30 lalatenduM gem, cool
12:31 lalatenduM hchiramm, then you are right
12:31 hchiramm lalatenduM, np :)
12:32 lalatenduM gem, btw we cant do run for each commit
12:32 hchiramm lalatenduM, gem yep
12:32 lalatenduM gem, Coverity website has a restriction for howmany runs we can do , depending on our code size
12:32 hchiramm as mentioned in the review comment we need to put a time line for notification
12:32 lalatenduM gem, and AFAIR it is 2 runs per week
12:32 hchiramm more or less , it will spam our gluster-devel
12:33 gem lalatenduM, as we have disabled the travis build I don't think it will ever send out emails.  it is completely up to coverity
12:33 gem lalatenduM, frequency - yes.. will change that
12:33 lalatenduM gem, thanks
12:34 ira joined #gluster-dev
12:38 nkhare joined #gluster-dev
12:57 kshlm lalatenduM, hchiramm, If you want to send coverity notifications to gluster devel, you can just add gluster-devel to the existing coverity setup.
12:57 nkhare_ joined #gluster-dev
12:57 hchiramm kshlm, yep. doing that way
12:57 nkhare_ joined #gluster-dev
12:58 kbyrne joined #gluster-dev
12:58 tdasilva primusinterpares: ping
12:58 glusterbot tdasilva: Please don't naked ping. http://blogs.gnome.org/mark​mc/2014/02/20/naked-pings/
12:59 kshlm hchiramm, I just went through the conversation, and thought you were setting up travis just for that one feature,
12:59 hchiramm lalatenduM, ^^^
12:59 kshlm Do you want me to do it?
13:00 hchiramm kshlm, please wait.. I was not sure abt the exact requirement
13:00 hchiramm it came from lalatenduM , so he can tell more abt it
13:00 kshlm I don't think there should be any problem.
13:00 hchiramm afaict, right now travis and coverity both are configured for sending the coverity notification to gluster-devel
13:01 kshlm We've not merged the travis patch yet, so there should be no trouble from travis.
13:01 kshlm And coverity doesn't yet send mails to the mailing list.
13:01 hchiramm yep, its not merged
13:01 kshlm I'll do it. It's just going to be a one email a week at max.
13:02 hchiramm LGTm
13:04 kshlm We need one of the list admins to accept the mail.
13:04 kshlm s/mail/request mail/
13:05 kshlm and then allow mails from coverity on the list.
13:06 hchiramm k..
13:09 kshlm So we are done.
13:09 hchiramm cool :)
13:09 kshlm We should be recieving periodic coverity reports on new defects on gluster-devel.
13:09 hchiramm kshlm++
13:09 glusterbot hchiramm: kshlm's karma is now 5
13:13 xavih joined #gluster-dev
13:18 rafi joined #gluster-dev
13:18 anrao joined #gluster-dev
13:19 lalatenduM kshlm, the travis stuff to do automated biweekly Coverity runs
13:19 lalatenduM kshlm, previously I had do the runs from my laptop manually
13:42 hagarth joined #gluster-dev
13:44 kkeithley1 joined #gluster-dev
13:49 prasanth_ joined #gluster-dev
14:12 kkeithley1 joined #gluster-dev
14:25 xavih joined #gluster-dev
14:28 shyam joined #gluster-dev
14:30 tdasilva joined #gluster-dev
14:43 kshlm joined #gluster-dev
14:43 kshlm joined #gluster-dev
15:05 kshlm joined #gluster-dev
15:21 wushudoin joined #gluster-dev
15:54 jobewan joined #gluster-dev
15:59 hagarth joined #gluster-dev
16:23 lpabon joined #gluster-dev
16:23 anrao joined #gluster-dev
16:29 shubhendu_ joined #gluster-dev
16:34 kshlm joined #gluster-dev
17:14 nishanth joined #gluster-dev
17:30 bala joined #gluster-dev
17:33 gem joined #gluster-dev
18:17 jobewan joined #gluster-dev
18:47 kanagaraj joined #gluster-dev
19:26 jobewan joined #gluster-dev
20:08 badone joined #gluster-dev
20:27 hagarth joined #gluster-dev
22:44 jobewan joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary