Hi Eric,
We cannot just ignore the failure since it's a regression. Here is what we
can do to proceed with your checkin ( I discussed this with Anoop and
Atanu).
You can create a JIRA and capture the BT of this corefile. Then disable this
test in regres/tools/runregr_core.ksh In the JIRA just
Issue is on predicatePushdownV2 branch derived from trafodion master branch.
Does that mean that we can ignore the failure and accept the merge in master
on PR255?
Eric
-Original Message-
From: Sandhya Sundaresan [mailto:sandhya.sundare...@esgyn.com]
Sent: Thursday, January 21, 2016 3:23
RE: I am puzzled with a jenkins test failure on CORE/TESTRTS
Looks like some problem with runtime stats (RTS). It is missing.
There was an issue related to missing RTS area on another branch.
Not sure if that has been merged in here. We can check that.
Selva can comment some more but he is on
There were 2 instances earlier (see attached) and Selva had requested we set
ABORT_ON_ERROR=8926 be set in the Jenkins environment so he could debug if
the issue happened again. Steve mentioned the ABORT_ON_ERROR is still on.
Hence we see the core file. I know Selva had problems figuring out why
Thanks!
On Thu, Jan 21, 2016 at 2:49 PM, Steve Varnau
wrote:
> Hi folks,
>
>
>
> I have updated jenkins pull-request testing to depend on which files are
> modified (or added/deleted). If any files in the docs/ directory tree is
> modified, it runs a simple build job
Thanks Steve, it really simplifies for documents check-in.
Br,
Seth
-Original Message-
From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
Sent: 2016年1月22日 6:47
To: dev@trafodion.incubator.apache.org
Subject: Re: Update to jenkins test for docs
Thanks!
On Thu, Jan 21, 2016 at 2:49