Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roachtest: pgjdbc failed #76231

Closed
cockroach-teamcity opened this issue Feb 8, 2022 · 5 comments · Fixed by #76476
Closed

roachtest: pgjdbc failed #76231

cockroach-teamcity opened this issue Feb 8, 2022 · 5 comments · Fixed by #76476
Assignees
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)

Comments

@cockroach-teamcity
Copy link
Member

roachtest.pgjdbc failed with artifacts on master @ a7b1c17c240c935056f87f29dfc1ee75611c371e:

The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/pgjdbc/run_1
	orm_helpers.go:191,orm_helpers.go:117,java_helpers.go:220,pgjdbc.go:188,pgjdbc.go:200,test_runner.go:779: 
		Tests run on Cockroach v22.1.0-alpha.1-975-ga7b1c17c24
		Tests run against pgjdbc REL42.2.19
		5298 Total Tests Run
		4555 tests passed
		743 tests failed
		60 tests skipped
		185 tests ignored
		4 tests passed unexpectedly
		0 tests failed unexpectedly
		0 tests expected failed but skipped
		0 tests expected failed but not run
		---
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		For a full summary look at the pgjdbc artifacts 
		
		An updated blocklist (pgjdbcBlockList22_1) is available in the artifacts' pgjdbc log
Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

/cc @cockroachdb/sql-experience

This test on roachdash | Improve this report!

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels Feb 8, 2022
@blathers-crl blathers-crl bot added the T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) label Feb 8, 2022
@rafiss rafiss self-assigned this Feb 8, 2022
@rafiss rafiss removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Feb 8, 2022
@cockroach-teamcity
Copy link
Member Author

roachtest.pgjdbc failed with artifacts on master @ 432a383c1a7509762ce66a2b9ae7869d82da5f31:

The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/pgjdbc/run_1
	orm_helpers.go:191,orm_helpers.go:117,java_helpers.go:220,pgjdbc.go:188,pgjdbc.go:200,test_runner.go:779: 
		Tests run on Cockroach v22.1.0-alpha.1-1019-g432a383c1a
		Tests run against pgjdbc REL42.2.19
		5298 Total Tests Run
		4555 tests passed
		743 tests failed
		60 tests skipped
		185 tests ignored
		4 tests passed unexpectedly
		0 tests failed unexpectedly
		0 tests expected failed but skipped
		0 tests expected failed but not run
		---
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		For a full summary look at the pgjdbc artifacts 
		
		An updated blocklist (pgjdbcBlockList22_1) is available in the artifacts' pgjdbc log
Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.pgjdbc failed with artifacts on master @ 84a0e500920e6d0b935d2007de256e42822e94c7:

The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/pgjdbc/run_1
	orm_helpers.go:191,orm_helpers.go:117,java_helpers.go:220,pgjdbc.go:188,pgjdbc.go:200,test_runner.go:779: 
		Tests run on Cockroach v22.1.0-alpha.1-1115-g84a0e50092
		Tests run against pgjdbc REL42.2.19
		5298 Total Tests Run
		4549 tests passed
		749 tests failed
		60 tests skipped
		185 tests ignored
		0 tests passed unexpectedly
		2 tests failed unexpectedly
		0 tests expected failed but skipped
		0 tests expected failed but not run
		---
		--- FAIL: org.postgresql.test.jdbc4.ConnectionValidTimeoutTest.testIsValidRespectsSmallerTimeout[networkTimeoutMillis=0, validationTimeoutSeconds=1, expectedMaxValidationTimeMillis=1,100] - unknown (unexpected)
		--- FAIL: org.postgresql.test.jdbc4.ConnectionValidTimeoutTest.testIsValidRespectsSmallerTimeout[networkTimeoutMillis=1,500, validationTimeoutSeconds=1, expectedMaxValidationTimeMillis=1,100] - unknown (unexpected)
		For a full summary look at the pgjdbc artifacts 
		
		An updated blocklist (pgjdbcBlockList22_1) is available in the artifacts' pgjdbc log
Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@rafiss
Copy link
Collaborator

rafiss commented Feb 11, 2022

the new failures may relate to #67501

craig bot pushed a commit that referenced this issue Feb 12, 2022
76394: sql: use IndexFetchSpec in TableReader r=RaduBerinde a=RaduBerinde

#### row: replace fetcher args with IndexFetchSpec

This commit replaces the row fetcher table args with IndexFetchSpec.

Release note: None

#### sql: use IndexFetchSpec in TableReader

This commit removes the table descriptor from TableReader and replaces
it with an IndexFetchSpec.

Eventually, we will use the same `IndexFetchSpec` to form the columnar
batch directly in KV.

Release note: None


76415: dev: address a few paper cuts r=irfansharif a=irfansharif

See individual commits, works through a few of the known paper cuts with dev/bazel (#75453).

76420: sql: initialize tenant span config with rangefeeds enabled r=irfansharif a=ajwerner

Not doing this causes problems when we construct new tenants as they won't be
able to establish a rangefeed until their first full reconciliation completes
and then propagates.

Even this is not great. If the preceding range did not have rangefeeds enabled,
it would take a closed timestamp interval for this enablement to propagate.
Perhaps this is evidence that we should always carve out a span at the end of
the keyspace and set it to have rangefeeds enabled.

I'll leave that fix and testing of this to somebody else. Hope this is helpful
enough on its own. cc `@irfansharif`  and `@arulajmani.` I believe this problem
has been blocking `@RaduBerinde.`

Fixes #76331

Release note: None

76437: clisqlshell: handle interactive query cancellation r=rafiss a=knz

Fixes #76433. 

As of this PR, there's a bug in lib/pq which forces the session to
terminate when any query gets cancelled. We find this unacceptable
and we plan to fix it later.

Release note (cli change): The interactive SQL shell (`cockroach sql`,
`cockroach demo`) now supports interrupting a currently running
query with Ctrl+C, without losing access to the shell.

76442: roachtest: try to stabilize ORM nightlies r=RichardJCai a=rafiss

fixes #76428
fixes #76426
fixes #68363
touches #76231
touches #76016
touches #76011

Ruby-pg and psycopg2 tests started passing because we now support pgwire
cancel.

Other tests (Django, Hibernate, and PGJDBC) seem flaky after the testing
settings change, so try to use slightly more conservative values.

Release note: None

76450: ci: add extra logging of `$TC_SERVER_URL` in pebble metamorphic nightly r=nicktrav a=rickystewart

Release note: None

Co-authored-by: Radu Berinde <[email protected]>
Co-authored-by: irfan sharif <[email protected]>
Co-authored-by: Andrew Werner <[email protected]>
Co-authored-by: Raphael 'kena' Poss <[email protected]>
Co-authored-by: Rafi Shamim <[email protected]>
Co-authored-by: Ricky Stewart <[email protected]>
@cockroach-teamcity
Copy link
Member Author

roachtest.pgjdbc failed with artifacts on master @ 80f1c2ce09389f1d7e97376964d3f2a922405b1b:

The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/pgjdbc/run_1
	orm_helpers.go:191,orm_helpers.go:117,java_helpers.go:220,pgjdbc.go:188,pgjdbc.go:200,test_runner.go:779: 
		Tests run on Cockroach v22.1.0-alpha.1-1182-g80f1c2ce09
		Tests run against pgjdbc REL42.2.19
		5298 Total Tests Run
		4553 tests passed
		745 tests failed
		60 tests skipped
		185 tests ignored
		4 tests passed unexpectedly
		2 tests failed unexpectedly
		0 tests expected failed but skipped
		0 tests expected failed but not run
		---
		--- FAIL: org.postgresql.test.jdbc4.ConnectionValidTimeoutTest.testIsValidRespectsSmallerTimeout[networkTimeoutMillis=1,500, validationTimeoutSeconds=1, expectedMaxValidationTimeMillis=1,100] - unknown (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- FAIL: org.postgresql.test.jdbc4.ConnectionValidTimeoutTest.testIsValidRespectsSmallerTimeout[networkTimeoutMillis=0, validationTimeoutSeconds=1, expectedMaxValidationTimeMillis=1,100] - unknown (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		For a full summary look at the pgjdbc artifacts 
		
		An updated blocklist (pgjdbcBlockList22_1) is available in the artifacts' pgjdbc log
Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.pgjdbc failed with artifacts on master @ 260be01361ed7264a870e530397ed3529cd014f7:

The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/pgjdbc/run_1
	orm_helpers.go:191,orm_helpers.go:117,java_helpers.go:220,pgjdbc.go:188,pgjdbc.go:200,test_runner.go:779: 
		Tests run on Cockroach v22.1.0-alpha.1-1209-g260be01361
		Tests run against pgjdbc REL42.2.19
		5298 Total Tests Run
		4553 tests passed
		745 tests failed
		60 tests skipped
		185 tests ignored
		4 tests passed unexpectedly
		2 tests failed unexpectedly
		0 tests expected failed but skipped
		0 tests expected failed but not run
		---
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- FAIL: org.postgresql.test.jdbc4.ConnectionValidTimeoutTest.testIsValidRespectsSmallerTimeout[networkTimeoutMillis=0, validationTimeoutSeconds=1, expectedMaxValidationTimeMillis=1,100] - unknown (unexpected)
		--- FAIL: org.postgresql.test.jdbc4.ConnectionValidTimeoutTest.testIsValidRespectsSmallerTimeout[networkTimeoutMillis=1,500, validationTimeoutSeconds=1, expectedMaxValidationTimeMillis=1,100] - unknown (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithFixedParameter[3: autoCommit=NO, binary=FORCE] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.test32000Binds[2: autoCommit=NO, binary=REGULAR] - https://github.com/cockroachdb/cockroach/issues/26508 (unexpected)
		For a full summary look at the pgjdbc artifacts 
		
		An updated blocklist (pgjdbcBlockList22_1) is available in the artifacts' pgjdbc log
Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@craig craig bot closed this as completed in bbb473c Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants