-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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 [ProcedureTransactionTest failed] #119937
Comments
error is:
See the test code here for the SQL commands it is sending: https://github.com/pgjdbc/pgjdbc/blob/9effea487dca529dc5cb0e71600a8c6509819c56/pgjdbc/src/test/java/org/postgresql/test/jdbc3/EscapeSyntaxCallModeCallIfNoReturnTest.java#L33-L51 This is the same as #119208. PR #119493 was supposed to resolve it, but seems like there is still an issue. cc @yuzefovich |
roachtest.pgjdbc failed with artifacts on master @ ce5f34ea97475f45fa354e58aacf424779d0de49:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ f4dc2b59541e11cf06e2b948c7c37bf1aed21868:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 559994e230ac3776dd1188e66678cce9205ab345:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 72646a555214c0705781e440b9df585d5eea9511:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 41da9eccc216413c09cc66ad4c6bfa5f92c506e3:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 41da9eccc216413c09cc66ad4c6bfa5f92c506e3:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 431d56840cacdc86638ccb48e9f3bdc16897d341:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 2ac5657aef0fd878973191079b6f3aadbc9c9266:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 34caf9d2c267f95f6aef2713708806e6f14948d6:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 067e48d29b9093038f6fcf2074cd761ffdcd4fe2:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ 0b6de9c809f8a4df2ba943a8c9dd023adb03b01d:
Parameters:
|
roachtest.pgjdbc failed with artifacts on master @ a2f1f379ee52ceee2b2aa6769f1fa162f8d6b8a7:
Parameters:
Same failure on other branches
|
roachtest.pgjdbc failed with artifacts on master @ f0116ea373a2b87155e7f0264df4f783ce177360:
Parameters:
Same failure on other branches
|
roachtest.pgjdbc failed with artifacts on master @ 3060756a084cc437114d64265e79ace5720a7317:
Parameters:
Same failure on other branches
|
120844: workflows: run `examples-orms` on non-FIPS machines r=rail a=rickystewart This was an accident. Epic: CRDB-8308 Release note: None 120849: roachtest: update pgjdbc blocklist r=yuzefovich a=yuzefovich Two tests now pass. Also record two known failures tracked by 119937 as expected (I'm looking into them but we might need to accept these failures as expected, tbd). Addresses: #119937. Epic: None Release note: None Co-authored-by: Ricky Stewart <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]>
roachtest.pgjdbc failed with artifacts on master @ 4a9385cacb82e7a8d6d37e5d9a26a6b7c845aab6:
Parameters:
Same failure on other branches
|
Right now there are 4 failures around OUT parameters:
First two have the same root cause - the test expects error code 42809 CREATE OR REPLACE FUNCTION myiofunc(a INOUT int, b OUT int) AS 'BEGIN b := a; a := 1; END;' LANGUAGE plpgsql;
CALL myiofunc(1, 10); which does return 42809 code when run manually via SQL shell. It seems like it is a quirk of JDBC driver. Two other failures are a recently introduced bug being fixed in #120945. |
Never mind my last comment - the failure file has multiple errors and I only looked at the first one. There appears to be an issue with handling prepared statements. Here is a reproduction of one issue in the PGTest
|
roachtest.pgjdbc failed with artifacts on master @ c994982a8be5af89f594e115e897dd6d62cf99d8:
Parameters:
Same failure on other branches
|
roachtest.pgjdbc failed with artifacts on master @ c994982a8be5af89f594e115e897dd6d62cf99d8:
Parameters:
Same failure on other branches
|
Failure in
It seems like a flake given that the previous run on exactly the same SHA didn't trigger this failure, so I'm ignoring it, for now at least. |
roachtest.pgjdbc failed with artifacts on master @ 6df7436b6388eb7823b9f63a42aa75e1fbc89a85:
Parameters:
Same failure on other branches
|
roachtest.pgjdbc failed with artifacts on master @ ec9444f8287663777c5ebceff61bcd280491ba08:
Parameters:
Same failure on other branches
|
roachtest.pgjdbc failed with artifacts on master @ 460707194644edbf4c6258d09b46d9877c8eefa6:
Parameters:
Same failure on other branches
|
roachtest.pgjdbc failed with artifacts on master @ 0dce29441187eda187aad472543997b06c2b01ea:
Parameters:
Same failure on other branches
|
roachtest.pgjdbc failed with artifacts on release-24.1 @ 557f4e6fe89d683d49082d88ba5adf6660e8f16f:
Parameters:
Same failure on other branches
|
I have fixes for I still don't understand why we produce a different error code for
|
roachtest.pgjdbc failed with artifacts on master @ bf013ea0a5311726e65d37e8f047ce39ea2d5f10:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
This test on roachdash | Improve this report!
Jira issue: CRDB-36400
The text was updated successfully, but these errors were encountered: