Camelia, the Perl 6 bug

IRC log for #gluster-dev, 2013-04-01

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

All times shown according to UTC.

Time Nick Message
00:06 yinyin joined #gluster-dev
00:34 yinyin joined #gluster-dev
01:01 jules_ joined #gluster-dev
01:26 yinyin joined #gluster-dev
02:24 kshlm|AF1 joined #gluster-dev
02:24 awheeler joined #gluster-dev
02:34 bala1 joined #gluster-dev
02:37 jules_ joined #gluster-dev
02:39 ndevos joined #gluster-dev
02:43 awheeler_ joined #gluster-dev
02:56 badone joined #gluster-dev
02:56 bharata joined #gluster-dev
03:06 sgowda joined #gluster-dev
03:47 badone joined #gluster-dev
03:51 bala1 joined #gluster-dev
03:55 rastar joined #gluster-dev
04:02 hagarth joined #gluster-dev
04:14 raghu joined #gluster-dev
04:21 yinyin joined #gluster-dev
04:28 sripathi joined #gluster-dev
04:38 bala1 joined #gluster-dev
04:48 bala1 joined #gluster-dev
04:51 yinyin joined #gluster-dev
04:52 hagarth joined #gluster-dev
04:56 aravindavk joined #gluster-dev
05:21 deepakcs joined #gluster-dev
05:27 yinyin joined #gluster-dev
05:27 rastar joined #gluster-dev
05:38 test joined #gluster-dev
05:50 anmol joined #gluster-dev
05:56 vshankar joined #gluster-dev
06:00 sgowda joined #gluster-dev
06:03 mohankumar joined #gluster-dev
06:04 lalatenduM joined #gluster-dev
06:06 lala_ joined #gluster-dev
06:31 sripathi1 joined #gluster-dev
06:35 yinyin joined #gluster-dev
06:46 sripathi joined #gluster-dev
06:54 sripathi joined #gluster-dev
06:54 sgowda joined #gluster-dev
07:09 sripathi joined #gluster-dev
07:49 sripathi joined #gluster-dev
08:37 sripathi1 joined #gluster-dev
08:39 sripathi joined #gluster-dev
09:05 anmol joined #gluster-dev
09:36 deepakcs joined #gluster-dev
09:48 bharata joined #gluster-dev
10:23 spai joined #gluster-dev
10:52 sripathi joined #gluster-dev
11:15 hagarth joined #gluster-dev
11:52 hagarth joined #gluster-dev
11:58 yinyin_ joined #gluster-dev
12:22 hagarth joined #gluster-dev
12:42 vshankar joined #gluster-dev
13:15 awheeler_ joined #gluster-dev
13:38 yinyin_ joined #gluster-dev
14:08 wushudoin joined #gluster-dev
14:08 badone joined #gluster-dev
14:12 jbrooks joined #gluster-dev
14:19 lpabon joined #gluster-dev
14:21 awheeler_ kkeithley: Ping
14:27 kkeithley awheeler_: hi
14:27 awheeler_ kkeithley: Just added you as a reviewer to my patch for the multi-volume bug.
14:28 kkeithley http://review.gluster.org/4748 ?
14:28 awheeler_ Yeas
14:28 kkeithley okay
14:30 awheeler_ kkeithley: Also noticed, and mentioned in that review, that my changes were not actually tested by the jenkins build, even though they were supposed to be.  Any idea how to get that addressed?
14:30 mohankumar joined #gluster-dev
14:31 kkeithley I (or someone else with the privs) has to kick that off. You should have received an email about a minute ago saying that it succeeded.
14:31 kkeithley succeeded = passed
14:32 kkeithley I has. heh.
14:32 awheeler_ Specifically the ufounit test.  It ran, but did not include in the output the results of the ring test.
14:33 kkeithley I haven't figured out why some test output gets swallowed and others don't.
14:34 awheeler_ Well, the total number of tests suggests that it didn't run them -- at least, when I run the tests from master, the count quite a bit higher./
14:35 awheeler_ From master, including my patch, 130 tests are run.
14:36 kkeithley ufounit?
14:37 awheeler_ sure, on the jenkins page, there is regression, release, smoke, and ufounit
14:37 kkeithley I don't see a test for ring.py in the regression output.
14:37 awheeler_ Exactly!
14:37 kkeithley hmm
14:37 awheeler_ Ufounit runs the regression tests for ufo
14:38 awheeler_ And my submissions correctly caused that to run, but it didn't run against my patch.
14:38 awheeler_ And, there are ring tests in master already from junaid, so weird that I'm not even seeing those.
14:39 awheeler_ Here's the output from my run of unittest.sh: http://pastebin.com/9Vt4Dn5b
14:40 rastar joined #gluster-dev
14:41 kkeithley yup, dunno. I'm not very familiar with the unit test code. I'll compare notes with portante.
14:42 kkeithley once he gets here
14:42 awheeler_ Ok, thank you.
14:44 kkeithley yw
15:02 rastar joined #gluster-dev
15:11 rastar joined #gluster-dev
15:17 rastar1 joined #gluster-dev
15:44 hagarth joined #gluster-dev
15:44 H__ joined #gluster-dev
16:04 hagarth joined #gluster-dev
16:13 hagarth joined #gluster-dev
17:01 lalatenduM joined #gluster-dev
17:03 awheeler_ kkeithley: Shouldn't branch be the branch I created for the bug, instead of master: http://build.gluster.org/job​/regression/975/parameters/?
17:05 portante joined #gluster-dev
17:07 awheeler_ kkeithley: nm, I see it's applying a patch
17:07 lpabon joined #gluster-dev
17:20 johnmark portante: ping
17:20 johnmark portante: ^^^
17:21 portante johnmark: pong
17:21 johnmark portante: see questions re: unit tests, above
17:22 portante I just joined the channel, so I don't have any context.
17:22 bala joined #gluster-dev
17:22 johnmark ah! ok
17:23 johnmark 07:35 < awheeler_> From master, including my patch, 130 tests are run.
17:23 johnmark 07:37 < kkeithley> ufounit?
17:23 johnmark 07:37 < awheeler_> sure, on the jenkins page, there is regression, release, smoke, and ufounit
17:23 johnmark 07:37 < kkeithley> I don't see a test for ring.py in the regression output.
17:23 johnmark 07:37 < awheeler_> Exactly!
17:23 johnmark 07:38 < kkeithley> hmm
17:23 johnmark 07:38 < awheeler_> Ufounit runs the regression tests for ufo
17:23 johnmark 07:38 < awheeler_> And my submissions correctly caused that to run, but it didn't run against my patch.
17:23 johnmark 07:39 < awheeler_> And, there are ring tests in master already from junaid, so weird that I'm not even  seeing those.
17:23 johnmark 07:40 < awheeler_> Here's the output from my run of unittest.sh: http://pastebin.com/9Vt4Dn5b
17:23 johnmark 07:40 -!- rastar [~raghavend@122.172.174.134] has joined #gluster-dev
17:23 johnmark 07:42 < kkeithley> yup, dunno. I'm not very familiar with the unit test code. I'll compare notes with  portante.
17:23 johnmark 07:42 < kkeithley> once he gets here
17:23 johnmark 07:43 < awheeler_> Ok, thank you.
17:23 johnmark 07:44 < kkeithley> yw
17:24 portante so is the new unit in a new directory? And if so, does that new directory have an empty __init__.py file (to make it a Python module)?
17:25 awheeler_ portante: The unittest.sh works correctly with a normal checkout from master -- the ring tests are there.
17:25 awheeler_ Even before my patch, which adds to those tests.
17:27 portante I'll try out your patch from gerrit, sec ...
17:29 awheeler_ Looks like there are 3 missing tests, actually, not just ring: constraints and exceptions are also not listed.
17:33 portante Here is the output I see (F17, 1.4.8-3 of openstack swift installed)
17:33 portante http://pastebin.test.redhat.com/135075
17:34 awheeler_ Hmm, I can't resolve that host
17:36 johnmark portante: I think that requires a red hat VPN connection :)
17:36 portante yes, sorry, sec
17:38 portante awheeler_: https://gist.github.com/portante/5286410
17:39 awheeler_ Right, so you see the ring tests, though minus my patch.
17:39 portante that was your patch I checkout from gerrit, I thought, no?
17:40 portante See the first line of the gist ...
17:40 awheeler_ There's Junaid's original patch, and then mine after his.  Coverage should be 89% for ring.py
17:40 portante it is not because it is failing to import constraints_conf_int, right?
17:41 portante So if I move to an environment where I have that, the tests should run
17:42 awheeler_ Not sure, could be.  It is showing the correct number of stmts in coverage
17:43 awheeler_ And the right number of lines
17:43 portante that is what happens when you see attribute errors at the module level running tests
17:44 portante the constraints tests are not there because of the same thing
17:44 portante the exception tests are there, at 100%
17:46 awheeler_ Ok.  So any idea why the build system is not showing any ring tests?
17:47 awheeler_ And only 104 tests
17:47 portante What is the version of swift installed on the test system? Most likely it is an old version of swift, probably needs 1.7.6
17:47 awheeler_ Well, I am using 1.7.4 for my tests.
17:48 awheeler_ I don't have info yet on how to package up 1.7.6 -- waiting for the Beta for that info, and using 1.7.4 until then or more info becomes available.
17:49 badone joined #gluster-dev
17:50 portante I think you shoujld use 1.7.6 for your tests, at least, since we know UFO currently requires that.
17:50 portante Looks like official grizzly will be 1.8.0, so we should probably just switch to that version once the finalize the release.
17:50 awheeler_ Sure, can tell me how to do that -- using the RPMs for my setup.
17:51 awheeler_ For what I'm testing though, I don't think it matters.
17:51 portante You might be right, hope it works for you.
17:52 awheeler_ Unless the ring setup in swift has changed substantially so we don't have to override it.  My looking at the code suggests that we still would need to.
17:53 awheeler_ The patch that was submitted doesn't override all the relevant functions.
17:55 awheeler_ So, what I meant by doesn't matter, is that I think the same code is needed.
18:00 portante Okay, but the tests need to be run against the correct version of swift, which is 1.7.6, so running it against 1.7.4 will be shaky at best, not sure what is really working or not.
18:02 awheeler_ Not unreasonable.  Happy to find out how to use 1.7.6, or even 1.8.0, but still don't see why the gluster build system doesn't appear to be running the tests I created.
18:03 awheeler_ Perhaps because it requires the exceptions?
18:03 awheeler_ s/exceptions/constraints/
18:04 lpabon joined #gluster-dev
18:09 portante sec, talking with Kaleb
18:13 awheeler_ cool.  taking a stab at 1.7.6 integration with the current spec file
18:15 * awheeler_ back in a bit
18:48 jclift joined #gluster-dev
18:55 awheeler_ back
19:17 awheeler_ With a little adjustment to the patches and files list, I've built a 1.7.6 RPM from the ufo spec file.
19:23 jclift Sounds like a potential patch submission for review then. :)
19:31 kkeithley Yeah, I can build UFO with 1.7.6 too, but I'm getting the proxy server complaining about no xattr>=0.4, which it didn't do when I was using 1.7.4. Can't tell yet whether Swift added a pkg_config check for xattr that's breaking. Through google I see other people complaining about the same thing, not necessarily in Swift though.
19:32 awheeler_ Ah, that sounds familiar.  I thought I had tried 1.7.6 before and ran into other errors.  Working on 3 things at once, so haven't gotten much further than building the RPMs.  lol
20:13 awheeler_ So, independent of all that, is there something wrong with the UFO part of the gluster build System?
20:15 jbrooks joined #gluster-dev
20:16 noche joined #gluster-dev
20:19 noche Im using --xml option that works on centos but not on debian (gluster 3.3.1), Im using precompiled packages from gluster.org pub ftp
20:21 semiosis noche: confirmed :(
20:24 noche :( so it is a bug on the packaging process
20:26 semiosis idk about the diagnosis yet
20:26 semiosis could you pastie/gist example output from --xml on centos?
20:30 noche yes http://pastie.org/7272211
20:31 semiosis noche: thanks
20:31 semiosis i will file a bug based on your pastie and look into it soon
20:32 semiosis my guess is some issue linking to an xml library when building on debian/ubuntu, but need to dig in to confirm that
20:32 semiosis noche: what version of glusterfs are you using?
20:33 noche 3.3.1
20:35 noche 3.3.1-1 (package version on debian and centos)
20:37 semiosis thx
20:37 noche it is debian 6.0.6 and centos 6.3
20:39 semiosis and i tested on ubuntu precise (12.04) and got the same as your debian result
20:41 semiosis noche: i'm going to include your pastie in the bug report
20:41 noche perfect, no problem
20:44 semiosis Bug 947226
20:45 glusterbot Bug http://goo.gl/jEc9n unspecified, unspecified, ---, kaushal, NEW , CLI option --xml doesn't have any effect on debian/ubuntu
20:53 jdarcy joined #gluster-dev
23:41 badone joined #gluster-dev
23:49 jbrooks joined #gluster-dev

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