glusterfs.git/tests/basic, branch v3.4.0alpha

Tests: Basic pump test case

2013-02-03T19:37:44+00:00

Change-Id: I94666debd5ec271ce5404a77efc421c12928e134
BUG: 857549
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/4451
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

tests: skip time consuming mock builds for code-only changes

2013-01-29T18:29:03+00:00

tests/basic/rpm.t takes a bulk of the time for the regression tests.
Often the building of the rpm is not affected at all and therefor the
tests does not add any value.

With this change the rpmbuild/mock test will only be run when some
changes affect the build system. Changes affecting 'tests/', 'doc/',
'*.py', *.c' and '*.h' do not trigger the test anymore.

Change-Id: Ic188b9e26cde3113b2bdf9cd1fab56d9fd85a4b7
BUG: 904005
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/4429
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

self-heald basic tests

2013-01-22T06:08:08+00:00

Change-Id: I50e5c4a6712cfc0a7c544551ba1ff182d851f522
BUG: 861015
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/4401
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

tests: let basic/rpm.t cleanup after itself when not in DEBUG-mode

2012-12-19T21:10:34+00:00

The temporary working directory unders /var/tmp is not cleaned when
debugging of the test is disabled. The logic should be the othetr way
around.

With this correction, the output while running is reduced as well.
Nothing of the output contains useful information and clutters the
testing output for no reason.

BUG: 888743
Change-Id: Id7616ad41873f61fd5d435b380f98068f313d5a6
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/4340
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

tests: Added basic sanity test for all volume-status cmds

2012-12-18T00:42:09+00:00

Change-Id: I482a38ca9f67a5f4b4cbc96731cb68c3b442c2d4
BUG: 764966
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/4298
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

build: include OCF resource agents by default and package them

2012-12-12T18:58:45+00:00

This change introduces a glusterfs-resource-agents sub-package that
contains the Open Cluster Framework (OCF) Resource Agents (RA). It also
changes the build infrastructure to include the RA by default, making
them available for anyone who is interested in using them with a OCF
compatible Hight-Availability solution like Pacemaker.

Build the RPMs without RA:
$ make dist && rpmbuild -ta --without ocf *.gz

Build the RPMs with RA (default):
$ make dist && rpmbuild -ta *.gz

There is no need to run ./autogen.sh from within the .spec, the whole
autotools infrastructure is included in the 'make dist' tarball already.

This also adds a test-case which builds the rpms with mock for the
latest two EPEL releases.

Change-Id: I12ef5f30f466868825352376156fb4e56b135c58
BUG: 869559
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/4130
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

BD Backend: Test Cases

2012-11-29T17:40:42+00:00

BUG: 805138
Change-Id: I04c1b68cf02d55d1481137fe6bb2386c2ba958f3
Signed-off-by: M. Mohan Kumar 
Reviewed-on: http://review.gluster.org/4145
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

tests: Add volume utils in a new file

2012-11-24T07:27:33+00:00

Change-Id: Ie78d24ca466d4bddc5c0727ed8ed51707e1f2a34
BUG: 839595
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/4228
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

fuse-bridge: fix posix-only configuration

2012-11-19T09:17:47+00:00

Recent changes in fuse-resolver had broken the use case of having
a trivial configuration with only storage/posix translator. Fix
it and include a regression test to avoid breakage in the future.

Change-Id: I85cbcac4b5c2d3517dd03fd3dc6d07610697981b
BUG: 868478
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/4114
Tested-by: Gluster Build System 
Reviewed-by: Brian Foster 
Reviewed-by: Vijay Bellur

fuse: handle mountflags properly

2012-11-19T08:49:36+00:00

The internal mount API had no access to the generic
mountflags used by mount(2).

Thus the "ro" mount option that needs to be passed down to mount(2) as
as a mountflag was incorrectly mangled into the fuse-specific mount
parameter string (cf. http://review.gluster.com/655).

This commit fixes the internal API and the "ro" issue. It also adds a
check for the "rw" and "ro" mount options in tests/basic/mount.t.

Thanks to Csaba Henk (csaba@) for suggestions and proposing an updated
patch.

Change-Id: I7f7bf49ae44d148f5c16f10736a0e412fb8f5e67
BUG: 853895
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/4163
Reviewed-by: Csaba Henk 
Tested-by: Gluster Build System