Camelia, the Perl 6 bug

IRC log for #gluster-dev, 2012-11-28

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

All times shown according to UTC.

Time Nick Message
01:54 joaquim__ joined #gluster-dev
01:54 maxiz joined #gluster-dev
01:58 mohankumar joined #gluster-dev
02:09 sunus joined #gluster-dev
02:39 yliu joined #gluster-dev
02:53 bharata joined #gluster-dev
02:59 bulde1 joined #gluster-dev
03:10 sgowda joined #gluster-dev
03:36 bulde joined #gluster-dev
03:57 Tobarja joined #gluster-dev
03:58 Tobarja left #gluster-dev
04:21 bulde joined #gluster-dev
04:36 sripathi joined #gluster-dev
04:50 hagarth joined #gluster-dev
05:05 sripathi joined #gluster-dev
05:37 raghu joined #gluster-dev
05:52 sripathi joined #gluster-dev
06:07 mohankumar joined #gluster-dev
06:30 sripathi joined #gluster-dev
06:36 puebele joined #gluster-dev
06:40 bala1 joined #gluster-dev
06:51 sripathi joined #gluster-dev
06:53 maxiz joined #gluster-dev
07:44 lkoranda joined #gluster-dev
08:12 deepakcs joined #gluster-dev
08:18 overclk joined #gluster-dev
08:34 gbrand_ joined #gluster-dev
08:51 hagarth joined #gluster-dev
08:58 bulde mohankumar: ping
08:58 mohankumar bulde: pong
08:58 bulde just one question on bd-test cases (bd.t)
08:59 mohankumar bulde: yes?
08:59 bulde what happens if bd xlator is not built and we try to run this test
08:59 bulde i am seeing test, and it looks fine for me, but the issue is, i don't want all tests to fail just because bd was not built :-)
08:59 bulde other than that it can get a +2 from me
09:00 mohankumar bulde: yeah i get that point
09:01 bulde on top of my head, i am not sure of how programatically tell bd is present or not
09:02 bulde i think we should take different test case based on 'gluster start' output...
09:03 mohankumar bulde: i can run gluster bd help and based on return value assume bd is compiled or not
09:04 bulde mohankumar: ok, then we have to return success if bd is not present
09:04 bulde :-)
09:31 sripathi joined #gluster-dev
09:53 sripathi joined #gluster-dev
09:57 mdarade left #gluster-dev
10:07 sripathi joined #gluster-dev
10:16 hagarth joined #gluster-dev
10:26 sripathi joined #gluster-dev
11:15 maxiz joined #gluster-dev
11:38 hagarth joined #gluster-dev
12:22 kkeithley joined #gluster-dev
12:40 shireesh joined #gluster-dev
12:50 edward1 joined #gluster-dev
13:24 puebele1 joined #gluster-dev
13:35 shireesh joined #gluster-dev
15:26 jbautista joined #gluster-dev
15:52 maxiz joined #gluster-dev
15:57 _Bryan_ joined #gluster-dev
16:31 jbrooks joined #gluster-dev
16:40 kp_ joined #gluster-dev
16:41 kp_ jdarcy, I have responded to your questions on http://review.gluster.org/4230
16:42 mohankumar joined #gluster-dev
16:42 kp_ jdarcy, hope that provides the context that was missing in the patch on gerrit.
17:00 raghu joined #gluster-dev
17:02 puebele joined #gluster-dev
17:21 hagarth joined #gluster-dev
17:37 jdarcy kp_: If it's true parallelism, won't we need a lock?  Just checking both pointers would still be racy.
18:26 jbrooks joined #gluster-dev
18:30 Technicool joined #gluster-dev
20:17 itamarjp joined #gluster-dev
20:51 sghosh joined #gluster-dev
21:16 jdarcy_ joined #gluster-dev
21:24 gbrand__ joined #gluster-dev
21:36 sghosh1 joined #gluster-dev
21:39 shireesh joined #gluster-dev
21:42 45PABEK6R joined #gluster-dev

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