I have create a PR for this issue. And the regression has beed passed
Does anyone can review and merge it?
On Aug 8, 2017, at 09:41, Weiqing Xu <xuweiqing...@gmail.com> wrote:
I'll check the JDBC regression test to make sure all unused statement will
On Tue, Aug 8, 2017 at 7:28 AM, Selva Govindarajan <
> This error message is thrown if you have 14 or more statements active in a
> single connection. Please reduce the number of open statements in the
> connection. It is possible that the statement is not explicitly closed in
> these tests.
> -----Original Message-----
> From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> Sent: Monday, August 7, 2017 3:09 PM
> To: email@example.com
> Subject: Failure in JDBC tests on multiple pull requests
> I was looking at the outstanding pull requests today. I noticed that some
> JDBC-related changes are getting the following failure:
> 2017-08-04 05:27:18 Batch Update Failed, See next exception for details
> 2017-08-04 05:27:18 Invalid Parameter Value: VARCHAR data longer than
> column length: 1
> 2017-08-04 05:27:30 Running testBatchInsertFKNotExist......
> 2017-08-04 05:27:51 *** ERROR Server Process $ZSM0 has reached
> allowed depth for nowait operation from the process 0,15836. [2017-08-04
> 2017-08-04 05:28:12 Running testBatchUpsertDuplicate......
> 2017-08-04 05:28:27 Running testBatchInsertPkDuplicate......
> 2017-08-04 05:28:41 Running testBatchUpdateOverflow......
> 2017-08-04 05:28:48 Batch Update Failed, See next exception for details
> 2017-08-04 05:28:48 Invalid Parameter Value: VARCHAR data longer than
> column length: 1
> 2017-08-04 05:28:52 Running testBatchUpdatePkDuplicate......
> 2017-08-04 05:28:59 Batch Update Failed, See next exception for details
> 2017-08-04 05:28:59 *** ERROR The operation is prevented by a unique
> constraint. [2017-08-04 05:28:59]
> 2017-08-04 05:29:06 Running testBatchInsertPositive......
> 2017-08-04 05:29:14 Time consumption for batch inserting 10000 rows is
> 1867 milli seconds
> 2017-08-04 05:31:00 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 231.891 sec <<< FAILURE! - in BatchTest
> I don't see anything in the pull requests themselves that should cause
> Does anyone have an idea what might be doing it? I hate to get into a mode
> where we just repeatedly run tests until they pass without fixing the
> underlying problem.