On Thursday 07 May 2015 10:50 AM,
Sachin Pandit wrote:
----- Original Message -----From: "Vijay Bellur" <vbellur@xxxxxxxxxx> To: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx>, "Gluster Devel" <gluster-devel@xxxxxxxxxxx>, "Rafi Kavungal Chundattu Parambil" <rkavunga@xxxxxxxxxx>, "Aravinda" <avishwan@xxxxxxxxxx>, "Sachin Pandit" <spandit@xxxxxxxxxx>, "Raghavendra Bhat" <rabhat@xxxxxxxxxx>, "Kotresh Hiremath Ravishankar" <khiremat@xxxxxxxxxx> Sent: Wednesday, May 6, 2015 10:53:01 PM Subject: Re: spurious regression status 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/consoleFullRafi - 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/consoleAravinda/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?quota-anon-fd.t failure is consistent in NetBSD, whereas in linux apart from test failure mentioned in etherpad I did not see this failure again in the regression runs. However, I remember Pranith talking about hitting this issue again.* tests/features/glupy.t * nuked tests 7153, 7167, 7169, 7173, 7212Emmanuel'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: 8Raghu - 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 As per the Jenkins output uss.t is failing in this test case TEST stat $M0/.history/snap6/aaa And its failing with the below error. stat: cannot stat `/mnt/glusterfs/0/.history/snap6/aaa': No such file or directory Its bit strange as before doing this check the file is created in the mount point and then the snapshot is taken. I am not sure whether its not able to reach the file itself or its parent directory (which represents the snapshot of the volume i.e. in this case its /mnt/glusterfs/0/.history/snap6). So I have sent a patch to check for the parent directory (i.e. stat on it). It will help us get more information. http://review.gluster.org/10671 Regards, Raghavendra Bhat |
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel