You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by Dave Birdsall <da...@esgyn.com> on 2017/08/16 17:34:16 UTC
Jenkins tests failing in JDBC tests
Hi Trafodion developers,
I'm noticing that almost all outstanding pull requests are failing the Jenkins tests with the same error. The error is in the jdbc_test-cdh suite:
2017-08-16 01:12:27 Running testBatchInsertFKNotExist......
2017-08-16 01:12:56 Batch Update Failed, See next exception for details
2017-08-16 01:12:56 *** ERROR[8103] The operation is prevented by referential integrity constraint TRAFODION.T4QA.BATCH_TEST_TABLE_FK_911645628_4551 on table TRAFODION.T4QA.BATCH_TEST_TABLE_FK.
2017-08-16 01:13:11 *** ERROR[2026] Server Process $ZSM0 has reached allowed depth for nowait operation from the process 0,15846. [2017-08-16 01:13:11]
I know that Weiqing is working hard on a solution to this problem.
In the meantime, though, I wonder if we should liberalize our commit policy and allow commits of pull requests if this is the only failure seen?
What do you think?
Dave
RE: Jenkins tests failing in JDBC tests
Posted by Selva Govindarajan <se...@esgyn.com>.
There were around 13 statements in OPEN or FETCH statement with the source string "select dataOffset, chunkLen, stringParam from table(ghost table "TRAFODION"."T4QA"."LOBDescChunks__08574991311373262837_0002") where descPartnKey = and descSyskey = "
These internal statements should be closed for the jdbc_test_cdh to pass or comment out the tests that trigger these internal statements for time being.
It is strange how these tests were enabled without going through the check-PR jobs. Check-PR jobs should have failed in the PR that enabled these tests. It is possible that the PR 1188 https://github.com/apache/incubator-trafodion/pull/1188 and the PR to enable the LOB tests https://github.com/apache/incubator-trafodion/pull/1167 were check-PR-ed around the same time without stepping on each other.
-----Original Message-----
From: Liu, Ming (Ming) [mailto:ming.liu@esgyn.cn]
Sent: Wednesday, August 16, 2017 7:30 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Jenkins tests failing in JDBC tests
+1
Ming
-----Original Message-----
From: Zalo Correa [mailto:zalo.correa@esgyn.com]
Sent: Thursday, August 17, 2017 1:48 AM
To: dev@trafodion.incubator.apache.org
Subject: RE: Jenkins tests failing in JDBC tests
+1
Zalo
-----Original Message-----
From: Sean Broeder [mailto:sean.broeder@esgyn.com]
Sent: Wednesday, August 16, 2017 10:45 AM
To: dev@trafodion.incubator.apache.org
Subject: RE: Jenkins tests failing in JDBC tests
Seems like a reasonable short-term solution to me.
+1
Sean
-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
Sent: Wednesday, August 16, 2017 10:34 AM
To: dev@trafodion.incubator.apache.org
Subject: Jenkins tests failing in JDBC tests
Hi Trafodion developers,
I'm noticing that almost all outstanding pull requests are failing the Jenkins tests with the same error. The error is in the jdbc_test-cdh suite:
2017-08-16 01:12:27 Running testBatchInsertFKNotExist......
2017-08-16 01:12:56 Batch Update Failed, See next exception for details
2017-08-16 01:12:56 *** ERROR[8103] The operation is prevented by referential integrity constraint TRAFODION.T4QA.BATCH_TEST_TABLE_FK_911645628_4551 on table TRAFODION.T4QA.BATCH_TEST_TABLE_FK.
2017-08-16 01:13:11 *** ERROR[2026] Server Process $ZSM0 has reached allowed depth for nowait operation from the process 0,15846. [2017-08-16 01:13:11]
I know that Weiqing is working hard on a solution to this problem.
In the meantime, though, I wonder if we should liberalize our commit policy and allow commits of pull requests if this is the only failure seen?
What do you think?
Dave
RE: Jenkins tests failing in JDBC tests
Posted by "Liu, Ming (Ming)" <mi...@esgyn.cn>.
+1
Ming
-----Original Message-----
From: Zalo Correa [mailto:zalo.correa@esgyn.com]
Sent: Thursday, August 17, 2017 1:48 AM
To: dev@trafodion.incubator.apache.org
Subject: RE: Jenkins tests failing in JDBC tests
+1
Zalo
-----Original Message-----
From: Sean Broeder [mailto:sean.broeder@esgyn.com]
Sent: Wednesday, August 16, 2017 10:45 AM
To: dev@trafodion.incubator.apache.org
Subject: RE: Jenkins tests failing in JDBC tests
Seems like a reasonable short-term solution to me.
+1
Sean
-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
Sent: Wednesday, August 16, 2017 10:34 AM
To: dev@trafodion.incubator.apache.org
Subject: Jenkins tests failing in JDBC tests
Hi Trafodion developers,
I'm noticing that almost all outstanding pull requests are failing the Jenkins tests with the same error. The error is in the jdbc_test-cdh suite:
2017-08-16 01:12:27 Running testBatchInsertFKNotExist......
2017-08-16 01:12:56 Batch Update Failed, See next exception for details
2017-08-16 01:12:56 *** ERROR[8103] The operation is prevented by referential integrity constraint TRAFODION.T4QA.BATCH_TEST_TABLE_FK_911645628_4551 on table TRAFODION.T4QA.BATCH_TEST_TABLE_FK.
2017-08-16 01:13:11 *** ERROR[2026] Server Process $ZSM0 has reached allowed depth for nowait operation from the process 0,15846. [2017-08-16 01:13:11]
I know that Weiqing is working hard on a solution to this problem.
In the meantime, though, I wonder if we should liberalize our commit policy and allow commits of pull requests if this is the only failure seen?
What do you think?
Dave
RE: Jenkins tests failing in JDBC tests
Posted by Zalo Correa <za...@esgyn.com>.
+1
Zalo
-----Original Message-----
From: Sean Broeder [mailto:sean.broeder@esgyn.com]
Sent: Wednesday, August 16, 2017 10:45 AM
To: dev@trafodion.incubator.apache.org
Subject: RE: Jenkins tests failing in JDBC tests
Seems like a reasonable short-term solution to me.
+1
Sean
-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
Sent: Wednesday, August 16, 2017 10:34 AM
To: dev@trafodion.incubator.apache.org
Subject: Jenkins tests failing in JDBC tests
Hi Trafodion developers,
I'm noticing that almost all outstanding pull requests are failing the Jenkins tests with the same error. The error is in the jdbc_test-cdh suite:
2017-08-16 01:12:27 Running testBatchInsertFKNotExist......
2017-08-16 01:12:56 Batch Update Failed, See next exception for details
2017-08-16 01:12:56 *** ERROR[8103] The operation is prevented by referential integrity constraint TRAFODION.T4QA.BATCH_TEST_TABLE_FK_911645628_4551 on table TRAFODION.T4QA.BATCH_TEST_TABLE_FK.
2017-08-16 01:13:11 *** ERROR[2026] Server Process $ZSM0 has reached allowed depth for nowait operation from the process 0,15846. [2017-08-16 01:13:11]
I know that Weiqing is working hard on a solution to this problem.
In the meantime, though, I wonder if we should liberalize our commit policy and allow commits of pull requests if this is the only failure seen?
What do you think?
Dave
RE: Jenkins tests failing in JDBC tests
Posted by Sean Broeder <se...@esgyn.com>.
Seems like a reasonable short-term solution to me.
+1
Sean
-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
Sent: Wednesday, August 16, 2017 10:34 AM
To: dev@trafodion.incubator.apache.org
Subject: Jenkins tests failing in JDBC tests
Hi Trafodion developers,
I'm noticing that almost all outstanding pull requests are failing the Jenkins tests with the same error. The error is in the jdbc_test-cdh suite:
2017-08-16 01:12:27 Running testBatchInsertFKNotExist......
2017-08-16 01:12:56 Batch Update Failed, See next exception for details
2017-08-16 01:12:56 *** ERROR[8103] The operation is prevented by referential integrity constraint TRAFODION.T4QA.BATCH_TEST_TABLE_FK_911645628_4551 on table TRAFODION.T4QA.BATCH_TEST_TABLE_FK.
2017-08-16 01:13:11 *** ERROR[2026] Server Process $ZSM0 has reached allowed depth for nowait operation from the process 0,15846. [2017-08-16 01:13:11]
I know that Weiqing is working hard on a solution to this problem.
In the meantime, though, I wonder if we should liberalize our commit policy and allow commits of pull requests if this is the only failure seen?
What do you think?
Dave