Perl 6 - the future is here, just unevenly distributed

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

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

All times shown according to UTC.

Time Nick Message
00:26 DV joined #gluster-dev
00:29 badone_ joined #gluster-dev
00:33 badone__ joined #gluster-dev
00:51 _Bryan_ joined #gluster-dev
00:57 bala joined #gluster-dev
01:07 purpleidea joined #gluster-dev
01:21 ira joined #gluster-dev
01:30 purpleid1a joined #gluster-dev
02:21 purpleidea joined #gluster-dev
02:42 purpleidea joined #gluster-dev
02:42 purpleidea joined #gluster-dev
02:52 ira joined #gluster-dev
03:02 purpleidea joined #gluster-dev
03:04 kdhananjay joined #gluster-dev
03:41 spandit joined #gluster-dev
03:53 atinmu joined #gluster-dev
03:54 anrao joined #gluster-dev
04:04 itisravi joined #gluster-dev
04:05 nkhare joined #gluster-dev
04:23 kanagaraj joined #gluster-dev
04:36 gem joined #gluster-dev
04:42 purpleidea joined #gluster-dev
04:42 purpleidea joined #gluster-dev
04:52 ndarshan joined #gluster-dev
04:58 kotreshhr joined #gluster-dev
05:01 gem joined #gluster-dev
05:11 purpleidea joined #gluster-dev
05:15 lalatenduM joined #gluster-dev
05:23 gem joined #gluster-dev
05:24 bala joined #gluster-dev
05:26 kanagaraj joined #gluster-dev
05:38 hagarth joined #gluster-dev
05:39 vipulnayyar joined #gluster-dev
05:40 Manikandan joined #gluster-dev
05:40 purpleidea joined #gluster-dev
05:40 purpleidea joined #gluster-dev
05:41 soumya_ joined #gluster-dev
05:44 ashiq joined #gluster-dev
05:49 kshlm joined #gluster-dev
05:51 raghu joined #gluster-dev
05:51 vimal joined #gluster-dev
05:54 hgowtham joined #gluster-dev
06:03 overclk joined #gluster-dev
06:05 anrao joined #gluster-dev
06:07 ppai joined #gluster-dev
06:10 lalatenduM joined #gluster-dev
06:11 purpleidea joined #gluster-dev
06:11 purpleidea joined #gluster-dev
06:13 ashiq joined #gluster-dev
06:13 kotreshhr hagarth: The patch set 4 of http://review.gluster.org/#/c/10051/, got two regression runs, one passed and the other failed. Could it be taken in or it needs one more regression run?
06:17 rjoseph joined #gluster-dev
06:19 nishanth joined #gluster-dev
06:20 aravindavk joined #gluster-dev
06:26 hagarth kotreshhr: let me check
06:26 kdhananjay joined #gluster-dev
06:26 kotreshhr hagarth: thanks!
06:32 ashiq joined #gluster-dev
06:34 hchiramm joined #gluster-dev
06:53 aravindavk joined #gluster-dev
07:04 kanagaraj joined #gluster-dev
07:05 hgowtham joined #gluster-dev
07:10 atinmu joined #gluster-dev
07:12 overclk joined #gluster-dev
07:17 nishanth joined #gluster-dev
07:21 ndevos RaSTar, raghu, kshlm: do you know if anyone is looking into this glusterd/snapshot/rcu  compile issue in master? http://build.gluster.org/job/rackspace​-regression-2GB-triggered/6303/console
07:22 kshlm ndevos, yes.
07:23 kshlm jdarcy had started a mail thread on gluster-devel last night regarding this.
07:23 ndevos kshlm: ah, okay, thanks!
07:23 kshlm Fix is avaliable at https://review.gluster.org/10105
07:32 obnox hi *. how long does it usually take after submitting a CR to gerrit to have the results of the regression runs, i.e. have the verified column ticked in green or red-X-ed ?
07:33 kshlm obnox, ~2h
07:35 obnox hm. that is strange.
07:35 ndevos well, 2 hours for the test to run, sometimes a multiple of 2 hours waiting in the queue....
07:36 obnox all the patches I submitted last afternoon -- night have not been updated
07:36 obnox ah ok
07:36 obnox is there a link in the CR / gerrit where I can see the scheduled reg runs in jenkins?
07:36 ndevos but at the moment things are more broken than ever before, maybe testing has been stopped until https://review.gluster.org/10105 has been merged and other changes rebased
07:36 obnox (I did not find one, only see it after the results have been added)
07:37 obnox ndevos: ok
07:37 ndevos obnox: http://build.gluster.org/job/rac​kspace-regression-2GB-triggered/ and the (trend) link in the box there
07:38 obnox ndevos: ok, non of my CRs is waiting there
07:38 ndevos kshlm, hagarth: change 10105 has its regression running for over 2.5 hours now, could it be stuck? http://build.gluster.org/job/rackspace​-regression-2GB-triggered/6292/console
07:38 obnox none
07:38 ndevos obnox: maybe they got aborted because there is a build failure in the master branch :-/
07:39 nishanth joined #gluster-dev
07:40 obnox ndevos: but also that should have been noted in the CR?
07:40 kshlm ndevos, looks like it.
07:40 atinmu joined #gluster-dev
07:41 obnox ndevos: and speaking of the rebasing issues (related 10105): locally my patches rebase and build just fine. also the smoke tests succeeded.
07:41 kshlm Looks like the netbsd regression run is also stuck http://build.gluster.org/job/rackspace-n​etbsd7-regression-triggered/2699/console
07:41 ndevos obnox: it depends... failures get noted, cancellations mostly not - and because things are currently more broken than I have ever seen before, I do not (yet) know what happened overnight
07:42 kshlm I'll stop and retrigger both the jobs.
07:43 overclk joined #gluster-dev
07:44 obnox ndevos: ok thanks. fair enough.
07:46 kshlm Since every job is failing, can't we just stop the auto-triggered jobs while 10105 gets merged?
07:46 kshlm hagarth, ndevos ^ ?
07:47 ndevos kshlm: I guess we could
07:49 ndevos kshlm: I've disabled it here: http://build.gluster.org/job/rackspac​e-regression-2GB-triggered/configure -> [x] Disable build
07:49 ndevos all running tests should finish, but maybe we should just cancel those too
07:50 ndevos kshlm: you can manually start a regression test run through build.gluster.org/job/rack​space-regression-2GB/build
07:51 kshlm http://build.gluster.org/job/racksp​ace-regression-2GB-triggered/6309/ is the one I retriggered.
07:52 kshlm don't stop that.
07:52 ndevos :)
07:52 kshlm I'll be AFK for lunch (~30 minutes)
08:00 obnox ndevos: i found one of my regression runs:
08:00 obnox http://build.gluster.org/job/rackspace​-regression-2GB-triggered/6274/console
08:00 obnox it did not update the CR (http://review.gluster.org/#/c/10056)
08:00 obnox and build failed due to warnings treated as errors
08:02 ndevos obnox: yeah, thats the breakage we're facing now, possibly RET=2 means "SEVERE FAILURE!!! Dont tell anyone."
08:02 obnox ndevos: well it is 'just' a compile error
08:02 obnox due to -Werr apparently
08:03 obnox I noticed the warnings after a rebase, building locally
08:04 ndevos yeah, obviously, but its a little unclear why/when -Werror got introduced... 32-bit architectures tend to get compile warnings too, so we cant enable it by default in our buildsys
08:04 hagarth ndevos: JustinClift asked that question to enable -Wall -Werror for CentOS 6.x regression tests and I agreed to that on gluster-devel
08:04 hagarth hence the mess atm
08:05 ndevos hagarth: hmm, okay, but maybe we should set those parameters for architectures/distributions that we know that can get build with it?
08:07 hagarth ndevos: right now it is only for CentOS 6, x86_64 in regression tests afaiu
08:08 ndevos hagarth: yes, but that does not mean developers build with those options now, we need to catch them in their building/testing first
08:09 hagarth ndevos: so you suggest that we add it to our CFLAGS by default?
08:10 obnox that must have been introduced after tha patch that introduced the warnings ?
08:12 ndevos hagarth: yes, we should probably add it to our CFLAGS, at least for the common environments
08:13 hagarth obnox: the patch was the trigger for introduction of these flags in regression tests.
08:13 hagarth ndevos: sounds like a good idea to me
08:13 obnox hagarth: ah. but still a chicken'n'egg problem :)
08:14 hagarth obnox: right :), I just hope to have 10105 merged so that we'll be clean again.
08:14 ndevos hagarth: the build script in Jenkins is also used for other releases... I'm pretty sure there are some warning generated by those too :-/
08:15 * hagarth checks build.sh
08:15 * hagarth notices sudo make install CFLAGS="-g -O0 -Wall -Werror" -j 4 >/dev/null
08:16 hagarth ndevos: what other non CentOS/Fedora x86_64 environments make use of this script?
08:17 obnox about the changes that have been already sumbitted and survived smoke test and maybe even have review+2 - do we need to do anything about them or will they be treated automatically?
08:17 hagarth obnox: nothing special would be needed there, me or one of the maintainers will have those merged.
08:18 obnox hagarth: ok, thx
08:18 ndevos hagarth: none that I know, but CFLAGS on a 'make install' like are a little awkward? isn't there just a 'make' where the CFLAGS should get passed?
08:20 ndevos hagarth: many devs will run their tests on non-CentOS6 systems, I would like to spare them the extra patch submissions because building on CentOS-6 by Jenkins is done differently
08:21 * ndevos promised to visit the office today, he'll be back online from train in 10-15 minutes
08:24 aravindavk joined #gluster-dev
08:34 bala1 joined #gluster-dev
08:55 vipulnayyar joined #gluster-dev
08:58 purpleidea joined #gluster-dev
09:08 kdhananjay joined #gluster-dev
09:15 ira joined #gluster-dev
09:26 purpleidea joined #gluster-dev
09:31 itisravi joined #gluster-dev
09:36 kotreshhr joined #gluster-dev
09:39 itisravi_ joined #gluster-dev
09:39 kanagaraj joined #gluster-dev
09:40 kanagaraj joined #gluster-dev
09:46 kotreshhr1 joined #gluster-dev
09:46 kshlm hagarth, ping!
09:48 kshlm I just found out that KP's other change, 9493 which was dependent on the problematic 9492, prevents all the problems that arose.
09:49 kshlm I hadn't merged that because I had a small comment.
09:51 kshlm I was looking at rebasing 9493 on the problem fix change 10105, as I needed it for another change I'm working on.
09:51 aravindavk joined #gluster-dev
09:52 kshlm 9493 basically modifies all the changes I did in 10105, to the point that 10105 is not needed at all.
09:53 kshlm So now I have 2 options,
09:53 kshlm - Rebase 9493 after 10105 is merged and review/merge it, or
09:54 hgowtham joined #gluster-dev
09:55 kshlm - Do the small change required by 9493 and get it merged, and abandon 10105.
09:55 kshlm Both solve our issues. Any opinions on which to pick??
09:55 vipulnayyar joined #gluster-dev
09:57 atinmu hagarth, could you please consider http://review.gluster.com/9613 in your review list?
10:00 jiffin joined #gluster-dev
10:03 obnox kshlm: if 9493 supersedes 10105, it sounds more reasonable to abandon 10105 instead of doing all the efforts to merge / rebase ...
10:05 obnox kshlm: but that's just me, speaking generally, w/o knowing all the background :)
10:08 kshlm obnox, that was the reason I asked the question as well.
10:09 hagarth kshlm: how hard is the rebase?
10:09 kshlm But 10105 has just passed regression. So I guess we'll be mergeing it to unblock others quickly.
10:09 kshlm hagarth, Not too hard. I already have a rebased patch ready.
10:09 hagarth kshlm: ok, going ahead with merging 10105 and enabling regression
10:10 kshlm Cool.
10:11 hagarth done
10:15 obnox hagarth: so I should repush my outstanding CRs rebased?
10:16 kshlm obnox, yes.
10:16 obnox kk, doing it
10:16 kshlm If your CRs don't touch the files modified by 10105 you can just push the rebase button on the review page.
10:17 kotreshhr joined #gluster-dev
10:17 obnox kshlm: oh, ok, trying that
10:18 obnox cool that worked
10:28 itisravi_ joined #gluster-dev
10:43 hgowtham joined #gluster-dev
10:44 nkhare joined #gluster-dev
10:48 kanagaraj joined #gluster-dev
10:49 kanagaraj joined #gluster-dev
11:07 kkeithley1 joined #gluster-dev
11:29 kanagaraj joined #gluster-dev
11:42 soumya joined #gluster-dev
11:52 sac` joined #gluster-dev
11:53 nkhare joined #gluster-dev
12:02 sac joined #gluster-dev
12:31 hgowtham joined #gluster-dev
12:33 JustinClift Well, we're clearly going to need more slave VM's online at all times
12:33 * JustinClift spins up some more
12:35 kanagaraj_ joined #gluster-dev
12:36 shaunm joined #gluster-dev
12:49 kotreshhr left #gluster-dev
12:55 hagarth joined #gluster-dev
12:56 shyam joined #gluster-dev
13:14 DV joined #gluster-dev
13:19 soumya joined #gluster-dev
13:19 shyam joined #gluster-dev
13:32 firemanxbr joined #gluster-dev
13:38 shyam joined #gluster-dev
13:39 shyam2 joined #gluster-dev
13:44 hchiramm_ joined #gluster-dev
13:58 jiffin joined #gluster-dev
14:01 vipulnayyar joined #gluster-dev
14:06 jiffin joined #gluster-dev
14:06 kasturi joined #gluster-dev
14:13 overclk joined #gluster-dev
14:24 jiffin joined #gluster-dev
14:30 wushudoin joined #gluster-dev
14:38 hagarth joined #gluster-dev
14:39 DV__ joined #gluster-dev
14:49 deepakcs joined #gluster-dev
14:56 lpabon joined #gluster-dev
15:12 DV__ joined #gluster-dev
15:24 kkeithley_ ndevos: revert it
15:28 purpleidea joined #gluster-dev
15:35 ndevos kkeithley_: it doesnt really matter :)
15:35 ndevos kkeithley_: I'll post an updated one for the next beta, just dont merge that
15:36 hagarth joined #gluster-dev
15:52 vipulnayyar joined #gluster-dev
16:08 _Bryan_ joined #gluster-dev
16:15 kbyrne joined #gluster-dev
16:23 DV joined #gluster-dev
16:24 lalatenduM joined #gluster-dev
16:40 hagarth joined #gluster-dev
16:44 _Bryan_ joined #gluster-dev
17:08 shaunm joined #gluster-dev
17:08 shaunm joined #gluster-dev
18:10 DV joined #gluster-dev
18:13 purpleidea joined #gluster-dev
18:13 purpleidea joined #gluster-dev
18:15 _Bryan_ joined #gluster-dev
18:53 hagarth joined #gluster-dev
18:59 DV joined #gluster-dev
19:15 ernetas joined #gluster-dev
19:15 ernetas Hey guys!
19:15 ernetas How long does it usually take to release a patch and package it? I patched a bug in 3.6 (https://github.com/gluster/glusterfs/pull/31), but it seems that on my system (running Ubuntu 14.04, with Glusterfs from ppa:gluster/glusterfs-3.6), the script is slightly outdated from the Github version of the 3.6 branch, although it was modified 1 month ago. Also, my pull request seems to be to the master of glusterfs, will someone cherry pick it to the rele
19:18 ernetas The issue in short is that 3.6 essentially dropped support for volume files just because of these couple of lines misplaced. Would be very glad if it could be merged and packaged :) .
19:19 ernetas If this goes through, I'd be glad to do some more slight touches of refactoring for the mount script.
19:34 JustinClift ernetas: Ahhh, interesting.  That definitely sounds like something the packagers for the deb's will want to know about
19:34 JustinClift ernetas: Would you be ok to ask this on the gluster-devel mailing list?
19:35 JustinClift ernetas: Asking here might get a response... but I'm kinda thinking it's thursday evening for large parts of the Gluster dev community right before a long weekend.
19:35 JustinClift eg I wouldn't hold my breath ;)
19:41 _Bryan_ joined #gluster-dev
20:28 DV joined #gluster-dev
20:37 ernetas JustinClift: thanks :)
20:38 ernetas I think I'm mistaken about the script being outdated, as I was looking into release-3.6 branch, not v3.6.2 tag, which seems to match the script. But regarding the bug, I created BZ ticket and pushed a commit to master (https://bugzilla.redhat.co​m/show_bug.cgi?id=1208676). Hope I done everything right and this goes through :)
20:38 glusterbot Bug 1208676: urgent, unspecified, ---, bugs, NEW , No support for mounting volumes with volume files
21:02 lpabon joined #gluster-dev
21:08 JustinClift ernetas: Emailed gluster-devel as well?
21:08 JustinClift The BZ is definitely a good idea.  Seal the deal with an email to gluster-devel if you haven't already though. ;)
21:10 JustinClift ernetas: Welcome to the Gluster Developer Community btw. :)
21:36 glusterbot` joined #gluster-dev
21:37 bfoster1 joined #gluster-dev
21:40 sankarshan_away joined #gluster-dev
21:44 glusterbot joined #gluster-dev
21:57 _Bryan_ joined #gluster-dev
22:33 DV joined #gluster-dev
23:10 DV joined #gluster-dev
23:41 DV joined #gluster-dev

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