Well I ran the tests with 'DEBUG=1 prove ./tests/basic/foo.t', and it looks like the scripts are executing this command: 'gluster --mode=script volume info', which fails on my test system because I have no real glusterfs config on it (basically I did './configure && make && make install && run-tests'). So it looks like these are nothing to worry about. Still, the tests create and delete volumes later on in the script, so I dont really understand why the tests do a 'volume info' when no volumes have been created by that test yet. Oh, well... On Sun, May 12, 2013 at 8:16 AM, Jason Brooks <jbrooks@xxxxxxxxxx> wrote: > > > ----- Original Message ----- >> From: "John Smith" <lbalbalba@xxxxxxxxx> >> To: "Gluster Devel" <gluster-devel@xxxxxxxxxx>, "Krishnan Parthasarathi" <kparthas@xxxxxxxxxx> >> Sent: Friday, May 10, 2013 9:19:29 AM >> Subject: glusterfs test suite: No volumes present >> >> Hi, >> >> >> Im running the glusterfs tests ./run-tests.sh, and am getting a lot of >> this type of error : >> >> [18:03:02] ./tests/basic/mount.t ............................. 1/29 No >> volumes present >> [18:08:07] ./tests/basic/volume-status.t ..................... 1/14 No >> volumes present >> [18:08:26] ./tests/basic/volume.t ............................ 1/17 No >> volumes present >> [18:10:19] ./tests/bugs/bug-762989.t ......................... 1/7 No >> volumes present >> >> >> I would like to fix this before i continue. Does this have something >> to do with my test setup ? Should I have a free lvm2 volume lying >> around for the tests to run on or something ? > > You may need to yum install lvm2-devel ? > > Jason > >> >> >> >> >> Thanks, >> >> >> >> Regards, >> >> >> >> >> John Smith. >> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxx >> https://lists.nongnu.org/mailman/listinfo/gluster-devel >>
