Re: [Gluster-devel] spurious regression status
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@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] spurious regression status
On Thursday 07 May 2015 10:50 AM, Sachin Pandit wrote: - Original Message - From: Vijay Bellur vbel...@redhat.com To: Pranith Kumar Karampuri pkara...@redhat.com, Gluster Devel gluster-devel@gluster.org, Rafi Kavungal Chundattu Parambil rkavu...@redhat.com, Aravinda avish...@redhat.com, Sachin Pandit span...@redhat.com, Raghavendra Bhat rab...@redhat.com, Kotresh Hiremath Ravishankar khire...@redhat.com Sent: Wednesday, May 6, 2015 10:53:01 PM Subject: Re: [Gluster-devel] 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/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? 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, 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 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@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] spurious regression status
Hi, I sent a patch [1] for release-3.7 branch and it failed [2] in the below mentioned test case. * ./tests/basic/ec/ec-6-2.t (Wstat: 0 Tests: 325 Failed: 2) * Failed tests: 96, 116 I am not sure if the failure has anything to do with my patch. But, I will continue debugging on this. If any of you have information related to this, then your help is much appreciated I have updated the information regarding the failure in etherpad [3] as well [1] http://review.gluster.org/#/c/10524/ [2] http://build.gluster.org/job/rackspace-regression-2GB-triggered/8502/consoleFull [3] https://public.pad.fsfe.org/p/gluster-spurious-failures Thanks, Sachin Pandit. - Original Message - From: Pranith Kumar Karampuri pkara...@redhat.com To: Gluster Devel gluster-devel@gluster.org Sent: Wednesday, May 6, 2015 6:52:53 AM Subject: [Gluster-devel] spurious regression status 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 * ./tests/basic/ec/ec-12-4.t (Wstat: 0 Tests: 541 Failed: 1) * Failed test: 11 * http://build.gluster.org/job/rackspace-regression-2GB-triggered/8312/consoleFull * Hopefully fixed now! * ./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 * ./tests/basic/quota-anon-fd-nfs.t (failed-test: 21) * Happens in: master ( http://build.gluster.org/job/rackspace-regression-2GB-triggered/8147/consoleFull) * Being investigated by: ? * tests/bugs/snapshot/bug-1112559.t (Failed tests: 9, 11) * Happens in: master * Being investigated by: ? * tests/features/glupy.t * nuked tests 7153, 7167, 7169, 7173, 7212 * 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/ * 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 Please feel free to let us know if you take up something from this list. Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] spurious regression status
* 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. I'm still seeing this one quite a lot in logs, though the errors are being ignored. * 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. Same for this one. If we re-enabled result checking for these two, maybe half of our test runs would start failing again. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 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/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 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] spurious regression status
- Original Message - From: Vijay Bellur vbel...@redhat.com To: Pranith Kumar Karampuri pkara...@redhat.com, Gluster Devel gluster-devel@gluster.org, Rafi Kavungal Chundattu Parambil rkavu...@redhat.com, Aravinda avish...@redhat.com, Sachin Pandit span...@redhat.com, Raghavendra Bhat rab...@redhat.com, Kotresh Hiremath Ravishankar khire...@redhat.com Sent: Wednesday, May 6, 2015 10:53:01 PM Subject: Re: [Gluster-devel] 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/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? 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, 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 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] spurious regression status
On 05/07/2015 09:26 AM, Atin Mukherjee wrote: On 05/07/2015 01:24 AM, Jeff Darcy wrote: * 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. I'm still seeing this one quite a lot in logs, though the errors are being ignored. Yesterday I started looking into it. I will update once I progress on the analysis. http://review.gluster.org/#/c/10619/ should address it. ~Atin ~Atin * 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. Same for this one. If we re-enabled result checking for these two, maybe half of our test runs would start failing again. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel -- ~Atin ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
