tests: move all test-cases into component subdirectories

There are around 300 regression tests, 250 being in tests/bugs. Running
partial set of tests/bugs is not easy because this is a flat directory
with almost all tests inside.

It would be valuable to make partial test/bugs easier, and allow the use
of mulitple build hosts for a single commit, each running a subset of
the tests for a quicker result.

Additional changes made:
- correct the include path for *.rc shell libraries and *.py utils
- make the testcases pass checkpatch
- arequal-checksum in afr/self-heal.t was never executed, now it is
- include.rc now complains loudly if it fails to find env.rc

Change-Id: I26ffd067e9853d3be1fd63b2f37d8aa0fd1b4fea
BUG: 1178685
Reported-by: Emmanuel Dreyfus <manu@netbsd.org>
Reported-by: Atin Mukherjee <amukherj@redhat.com>
URL: http://www.gluster.org/pipermail/gluster-devel/2014-December/043414.html
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: http://review.gluster.org/9353
Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>

1 files changed, 0 insertions, 77 deletions

diff --git a/tests/bugs/bug-948729/bug-948729-mode-script.t b/tests/bugs/bug-948729/bug-948729-mode-script.t
deleted file mode 100644
index 6264e18f1bd..00000000000
--- a/tests/bugs/bug-948729/bug-948729-mode-script.t
+++ /dev/null
@@ -1,77 +0,0 @@
-#!/bin/bash
-
-. $(dirname $0)/../../include.rc
-. $(dirname $0)/../../volume.rc
-. $(dirname $0)/../../cluster.rc
-
-function check_peers {
-        $CLI_1 peer status | grep 'Peer in Cluster (Connected)' | wc -l
-}
-
-cleanup;
-
-uuid1=`uuidgen`;
-uuid2=`uuidgen`;
-uuid3=`uuidgen`;
-
-TEST launch_cluster 2;
-
-TEST $CLI_1 peer probe $H2;
-
-EXPECT_WITHIN $PROBE_TIMEOUT 1 check_peers;
-
-B3=/d/backends/3
-mkdir -p $B3
-
-TEST truncate -s 16M $B1/brick1
-TEST truncate -s 16M $B2/brick2
-TEST truncate -s 16M $B3/brick3
-
-TEST LD1=`SETUP_LOOP $B1/brick1`
-TEST MKFS_LOOP $LD1
-TEST LD2=`SETUP_LOOP $B2/brick2`
-TEST MKFS_LOOP $LD2
-TEST LD3=`SETUP_LOOP $B3/brick3`
-TEST MKFS_LOOP $LD3
-
-mkdir -p $B1/$V0 $B2/$V0 $B3/$V0
-
-TEST MOUNT_LOOP $LD1 $B1/$V0
-TEST MOUNT_LOOP $LD2 $B2/$V0
-TEST MOUNT_LOOP $LD3 $B3/$V0
-
-cli1=$(echo $CLI1 | sed 's/ --wignore//')
-
-#Case 0: Parent directory of the brick is absent
-TEST ! $cli1 volume create $V0 $H1:$B1/$V0/nonexistent/b1 $H2:$B2/$V0/nonexistent/b2
-
-#Case 1: File system root being used as brick directory
-TEST   ! $cli1 volume create $V0 $H1:$B1/$V0 $H2:$B2/$V0
-
-#Case 2: Brick directory contains only one component
-TEST   ! $cli1 volume create $V0 $H1:/$uuid1 $H2:/$uuid2
-
-#Case 3: Sub-directories of the backend FS being used as brick directory
-TEST   $cli1 volume create $V0 $H1:$B1/$V0/brick1 $H2:$B2/$V0/brick2
-
-#add-brick tests
-TEST ! $cli1 volume add-brick $V0 $H1:$B3/$V0/nonexistent/brick3
-TEST ! $cli1 volume add-brick $V0 $H1:$B3/$V0
-TEST ! $cli1 volume add-brick $V0 $H1:/$uuid3
-TEST   $cli1 volume add-brick $V0 $H1:$B3/$V0/brick3
-
-#####replace-brick tests
-#FIX-ME : replace-brick does not currently work in the newly introduced
-#####cluster test framework
-
-$CLI1 volume stop $V0
-
-UMOUNT_LOOP $B1/$V0
-UMOUNT_LOOP $B2/$V0
-UMOUNT_LOOP $B3/$V0
-
-rm -f  $B1/brick1
-rm -f  $B2/brick2
-rm -f  $B3/brick3
-
-cleanup;