glusterfs.git/tests/basic/quick-read-with-upcall.t, branch v7.1

tests/quick-read-upcall: mark it bad

2019-06-07T08:49:09+00:00

Frequent intermittent failures observed.
```
08:59:24 ok  11 [     10/      3] <  36> 'write_to /mnt/glusterfs/0/test.txt test-message1'
08:59:24 ok  12 [     10/      6] <  37> 'test-message1 cat /mnt/glusterfs/0/test.txt'
08:59:24 ok  13 [     10/      4] <  38> 'test-message0 cat /mnt/glusterfs/1/test.txt'
08:59:24 not ok  14 [   3715/      6] <  45> 'test-message1 cat /mnt/glusterfs/1/test.txt' -> 'Got "test-message0" instead of "test-message1"'
08:59:24 ok  15 [     10/    162] <  47> 'gluster --mode=script --wignore volume set patchy features.cache-invalidation on'
08:59:24 ok  16 [     10/    148] <  48> 'gluster --mode=script --wignore volume set patchy performance.qr-cache-timeout 15'
```

updates: bz#1718191
Change-Id: Ieb9e5a9a428995ff178f77bc4a5155b8298d3fa0
Signed-off-by: Amar Tumballi

tests/quick-read-with-upcall.t: increase the timeout

2019-05-21T11:41:43+00:00

Running with 2 second sleep at this place caused failures like:
`not ok  14 [   2014/      7] <  41> 'test-message1 cat /mnt/glusterfs/1/test.txt' -> 'Got "test-message0" instead of "test-message1"'`

in few runs in 100 iterations. But when increased to higher than sleep 3,
have not seen any failures in 100 runs.

While I don't know the exact reasons for the behavior yet, looks like this
increase in wait helps to pass the regression without failures.

updates: bz#1693692
Change-Id: I0610b79bea53e36de3eea6c11234b7fc9dfd6232
Signed-off-by: Amar Tumballi

tests: improve and fix some test scripts

2019-05-09T09:24:10+00:00

Change-Id: Iceefe22af754096c599dc570d4894d14fce4deae
Updates: bz#1193929
Signed-off-by: Xavier Hernandez

quick-read: Integrate quick read with upcall and increase cache time

2017-12-13T08:11:37+00:00

Fixes : #261
Co-author: Subha sree Mohankumar 
Change-Id: Ie9dd94e86459123663b9b200d92940625ef68eab
Signed-off-by: Poornima G