On Thu, Jan 28, 2016 at 12:10 PM, Atin Mukherjee
wrote:
>
>
> On 01/28/2016 12:00 PM, Raghavendra Talur wrote:
> > 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
On 01/28/2016 12:00 PM, Raghavendra Talur wrote:
> 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.
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 T
On Thu, Jan 28, 2016 at 11:17 AM, Atin Mukherjee
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 c
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.glu
