On Wednesday 06 May 2015 10:53 PM, Vijay Bellur wrote:
On 05/06/2015 06:52 AM, Pranith Kumar Karampuri wrote:
hi,
Please backport the patches that fix spurious regressions to 3.7
as well. This is the status of regressions now:
* ./tests/bugs/quota/bug-1035576.t (Wstat: 0 Tests: 24 Failed: 2)
* Failed tests: 20-21
*
http://build.gluster.org/job/rackspace-regression-2GB-triggered/8329/consoleFull
* ./tests/bugs/snapshot/bug-1112559.t: 1 new core files
*
http://build.gluster.org/job/rackspace-regression-2GB-triggered/8308/consoleFull
* One more occurrence -
* Failed tests: 9, 11
*
http://build.gluster.org/job/rackspace-regression-2GB-triggered/8430/consoleFull
Rafi - this seems to be a test unit contributed by you. Can you please
look into this one?
* ./tests/geo-rep/georep-rsync-changelog.t (Wstat: 256 Tests: 3
Failed: 0)
* Non-zero exit status: 1
*
http://build.gluster.org/job/rackspace-regression-2GB-triggered/8168/console
Aravinda/Kotresh - any update on this? If we do not intend enabling
geo-replication tests in regression runs for now, this should go off
the list.
* ./tests/basic/quota-anon-fd-nfs.t (failed-test: 21)
* Happens in: master
(http://build.gluster.org/job/rackspace-regression-2GB-triggered/8147/consoleFull)
<http://build.gluster.org/job/rackspace-regression-2GB-triggered/8147/consoleFull%29>
* Being investigated by: ?
Sachin - does this happen anymore or should we move it off the list?
* tests/features/glupy.t
* nuked tests 7153, 7167, 7169, 7173, 7212
Emmanuel's investigation should help us here. Thanks!
* tests/basic/volume-snapshot-clone.t
* http://review.gluster.org/#/c/10053/
* Came back on April 9
*
http://build.gluster.org/job/rackspace-regression-2GB-triggered/6658/
Rafi - does this happen anymore? If fixed due to subsequent commits,
we should look at dropping this test from is_bad_test() in run-tests.sh.
* tests/basic/uss.t
* https://bugzilla.redhat.com/show_bug.cgi?id=1209286
* http://review.gluster.org/#/c/10143/
* Came back on April 9
*
http://build.gluster.org/job/rackspace-regression-2GB-triggered/6660/
* ./tests/bugs/glusterfs/bug-867253.t (Wstat: 0 Tests: 9 Failed: 1)
* Failed test: 8
Raghu - does this happen anymore? If fixed due to subsequent commits,
we should look at dropping this test from is_bad_test() in run-tests.sh.
-Vijay
I tried to reproduce the issue and it did not happen in my setup. So I
am planning to get a slave machine and test it there.
Regards,
Raghavendra Bhat
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
