----- Original Message ----- > From: "Niels de Vos" <ndevos@xxxxxxxxxx> > To: "Atin Mukherjee" <amukherj@xxxxxxxxxx>, "Rajesh Joseph" <rjoseph@xxxxxxxxxx> > Cc: "Dan Lambright" <dlambrig@xxxxxxxxxx>, "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Monday, November 9, 2015 7:39:28 AM > Subject: Re: spurious regression errors getting worse > > On Fri, Nov 06, 2015 at 09:36:50AM +0530, Atin Mukherjee wrote: > > > > > > On 11/06/2015 07:47 AM, Dan Lambright wrote: > > > It seems to have become more difficult in the last week to pass > > > regression tests. > > > > > > I've started recording the tests that seem to be failing the most: > > > > > > bug-1221481-allow-fops-on-dir-split-brain.t > > > bug-1238706-daemons-stop-on-peer-cleanup.t > > You shouldn't be worried about > > bug-1238706-daemons-stop-on-peer-cleanup.t as its marked as bad. Also > > respective failure links for all these tests would help component owners > > to root cause the issues. Probably you could add all of them here [1] > > We really need to file bugs for the problems, it allows us to get > notifications about problems. Etherpads can be nice to dedicated work, > but many of us do not check them regularly. There does not seem to be a small core set of bugs that fails regularly. Rather, the set of spurious bugs seems to be large. So we would be filing a lot of bugs. But, it could be done. And is probably more effective than a rarely consulted ether pad. > > Rajesh, tests/bugs/snapshot/bug-1227646.t resulted in a core for this > run: > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/15664/consoleFull > > I'm not sure if someone is looking into that already? > > Thanks, > Niels > > > > > [1] https://public.pad.fsfe.org/p/gluster-spurious-failures > > > > Thanks, > > Atin > > > ./tests/bugs/quota/bug-1235182.t > > > ./tests/bugs/distribute/bug-1066798.t > > > ./tests/bugs/snapshot/bug-1166197.t > > > > > > In some cases regression must be run a half dozen times before finally > > > passing. > > > > > > Could the owners those tests please look into these? > > > _______________________________________________ > > > Gluster-devel mailing list > > > Gluster-devel@xxxxxxxxxxx > > > http://www.gluster.org/mailman/listinfo/gluster-devel > > > > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@xxxxxxxxxxx > > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
