glusterfs.git/tests/bugs/bug-895235.t, branch release-8

tests: move all test-cases into component subdirectories

2015-01-06T11:24:24+00:00

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 
Reported-by: Atin Mukherjee 
URL: http://www.gluster.org/pipermail/gluster-devel/2014-December/043414.html
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/9353
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Emmanuel Dreyfus 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

Regression test portability: dd usage

2014-07-14T13:29:15+00:00

NetBSD, FreeBSD, and MacOS X dd(1) bs argument uses m for megabyte, while
Linux uses M. Use bs=1024k instead of bs=1M for better compatibility.

BUG: 764655
Change-Id: I603f57adbc9b31f6d634b918726437fbfce42e03
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/8278
Tested-by: Gluster Build System 
Reviewed-by: Harshavardhana 
Reviewed-by: Justin Clift 
Reviewed-by: Vijay Bellur

tests: Avoid timing delays caused by fsync

2013-07-23T10:37:54+00:00

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

Tests: Fix latency calculation

2013-01-29T02:45:11+00:00

Idea is to make sure that the FINODELK max latency is not
in the order of seconds.

Change-Id: Ic47dc46c3b2d24d223fe7e2212c4c035de37c9ae
BUG: 895235
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/4434
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Gluster Build System

cluster/afr: Disable delayed post op when eager-lock is off

2013-01-18T23:57:56+00:00

Problem:
When eager-lock is disabled, inodelks for write-fops on same
fd conflict with each other. If eager-lock is disabled but
delayed post-op is enabled then each write fop's inodelk unlock
waits for post-op-delay-secs. So the conflicting write fop
acquires inodelk after post-op-delay-secs. This results in
post-op-delay-secs delay for every write fop on the fd for
sequential writes (Ex: dd).

Fix:
Disable delayed-post-op when eager-lock is off.

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