Ok, RCA: In NetBSD cores are being generated in /d/backends/*/*.core run-tests.sh looks only for "/core*" when looking for cores.
So, at the end of test run when regression.sh looks for core everywhere, it finds one and errors out. Should think of a solution which is generic. Will update. On Thu, Jan 28, 2016 at 11:37 AM, Raghavendra Talur <rta...@redhat.com> wrote: > > > On Thu, Jan 28, 2016 at 11:17 AM, Atin Mukherjee <amukh...@redhat.com> > wrote: > >> Are we running a different version of run-tests.sh in jenkin slaves. The >> reason of suspection is beacuse in last couple of runs [1] & [2] in >> NetBSD I am seeing no failures apart from bad tests but the regression >> voted failure and I can not make out any valid reason out of it. >> >> [1] >> >> https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13756/consoleFull >> [2] >> >> https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13755/consoleFull > > > > I checked the slave machine now. > regression.sh file is different but the run-tests.sh script is same. > > A wild guess here, is it possible that the core generation takes time and > when we check for a core right after a test is run it is not present yet? > Does anyone know how to work around that? > > >> >> ~Atin >> _______________________________________________ >> Gluster-infra mailing list >> gluster-in...@gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-infra >> > >
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
