Re: [Gluster-devel] reviving spurious failures tracking
On Wed, Jul 29, 2015 at 6:57 PM, Pranith Kumar Karampuri pkara...@redhat.com wrote: On 07/29/2015 06:56 PM, Pranith Kumar Karampuri wrote: On 07/29/2015 06:10 PM, Emmanuel Dreyfus wrote: On Wed, Jul 29, 2015 at 04:06:43PM +0530, Vijay Bellur wrote: - If there are tests that cannot be fixed easily in the near term, we move such tests to a different folder or drop such test units. A tests/disabled directory seemsthe way to go. But before going there, the test maintaniner should be notified. Perhaps we should have a list of contacts ina comment on the topof each test? Jeff already implemented bad-tests infra already. We can use the same? Check is_bad_test() in run-tests.sh tests/basic/mount-nfs-auth.t is failing very frequently on netbsd machines. The latest failure is https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/9296/consoleFull The test always passes when run in bash -x mode. It seems that timeout for test 51 and test 52 is sometimes not enough. Can any one from NFS team verify the same and increase the timeout if required? I will be moving the test to bad test list till this is fixed. Pranith 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 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] reviving spurious failures tracking
On Wednesday 29 July 2015 Vijay Bellur wrote: On Wednesday 29 July 2015 03:40 PM, Pranith Kumar Karampuri wrote: hi, I just updated https://public.pad.fsfe.org/p/gluster-spurious-failures with the latest spurious failures we saw in linux and NetBSD regressions. Could you guys update with any more spurious regressions that you guys are observing but not listed on the pad. Could you guys help in fixing these issues fast as the number of failures is increasing quite a bit nowadays. I think we have been very tolerant for failing tests and it is time to change this behavior. I propose that: - we block commits for components that have failing tests listed in the tracking etherpad. - once failing tests are addressed on a particular branch, normal patch merging can resume. - If there are tests that cannot be fixed easily in the near term, we move such tests to a different folder or drop such test units. We still have a couple tests with frequent, spurious failures. Let's please either get these fixed, or removed from the tree if they are fundamentally broken. Otherwise we'll have to invoke the nuclear option. ;-) -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] reviving spurious failures tracking
On Wednesday 29 July 2015 03:40 PM, Pranith Kumar Karampuri wrote: hi, I just updated https://public.pad.fsfe.org/p/gluster-spurious-failures with the latest spurious failures we saw in linux and NetBSD regressions. Could you guys update with any more spurious regressions that you guys are observing but not listed on the pad. Could you guys help in fixing these issues fast as the number of failures is increasing quite a bit nowadays. I think we have been very tolerant for failing tests and it is time to change this behavior. I propose that: - we block commits for components that have failing tests listed in the tracking etherpad. - once failing tests are addressed on a particular branch, normal patch merging can resume. - If there are tests that cannot be fixed easily in the near term, we move such tests to a different folder or drop such test units. Thoughts? Regards, Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] reviving spurious failures tracking
I have updated tiering related spurious failures to proper state. Regards Rafi KC On 07/29/2015 03:40 PM, Pranith Kumar Karampuri wrote: hi, I just updated https://public.pad.fsfe.org/p/gluster-spurious-failures with the latest spurious failures we saw in linux and NetBSD regressions. Could you guys update with any more spurious regressions that you guys are observing but not listed on the pad. Could you guys help in fixing these issues fast as the number of failures is increasing quite a bit nowadays. Tests to be fixed (Linux) tests/bugs/distribute/bug-1066798.t (http://build.gluster.org/job/rackspace-regression-2GB-triggered/12908/console) http://build.gluster.org/job/rackspace-regression-2GB-triggered/12908/console%29(http://build.gluster.org/job/rackspace-regression-2GB-triggered/12907/console) http://build.gluster.org/job/rackspace-regression-2GB-triggered/12907/console%29 tests/bitrot/bug-1244613.t (http://build.gluster.org/job/rackspace-regression-2GB-triggered/12906/console) http://build.gluster.org/job/rackspace-regression-2GB-triggered/12906/console%29 tests/bugs/snapshot/bug-1109889.t (http://build.gluster.org/job/rackspace-regression-2GB-triggered/12905/console) http://build.gluster.org/job/rackspace-regression-2GB-triggered/12905/console%29 tests/bugs/replicate/bug-1238508-self-heal.t (http://build.gluster.org/job/rackspace-regression-2GB-triggered/12904/console) http://build.gluster.org/job/rackspace-regression-2GB-triggered/12904/console%29 tests/basic/nufa.t (http://build.gluster.org/job/rackspace-regression-2GB-triggered/12902/console) http://build.gluster.org/job/rackspace-regression-2GB-triggered/12902/console%29 On NetBSD: tests/basic/mount-nfs-auth.t (http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8796/console) http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8796/console%29 tests/basic/tier/tier-attach-many.t (http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8789/console) http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8789/console%29 tests/basic/afr/arbiter.t (http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8785/console) http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8785/console%29 tests/basic/tier/bug-1214222-directories_miising_after_attach_tier.t (http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8784/console) http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8784/console%29 tests/basic/quota.t (http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8780/console) http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/8780/console%29 First step is to move the tests above to Tests being looked at: (please put your name against the test you are looking into): section by the respective developers. 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] reviving spurious failures tracking
On 07/29/2015 06:10 PM, Emmanuel Dreyfus wrote: On Wed, Jul 29, 2015 at 04:06:43PM +0530, Vijay Bellur wrote: - If there are tests that cannot be fixed easily in the near term, we move such tests to a different folder or drop such test units. A tests/disabled directory seemsthe way to go. But before going there, the test maintaniner should be notified. Perhaps we should have a list of contacts ina comment on the topof each test? Jeff already implemented bad-tests infra already. We can use the same? Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] reviving spurious failures tracking
On Wed, Jul 29, 2015 at 04:06:43PM +0530, Vijay Bellur wrote: - If there are tests that cannot be fixed easily in the near term, we move such tests to a different folder or drop such test units. A tests/disabled directory seemsthe way to go. But before going there, the test maintaniner should be notified. Perhaps we should have a list of contacts ina comment on the topof each test? -- Emmanuel Dreyfus m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
