Thread: Test suite failures?
(re-sending this--I tried yesterday but it looks like it failed without
a clear reason)
I've finally gotten the COPY functionality merge to a stable point and
wanted to run through the test suite, but I found that (even without
applying the COPY changes) I get a number of errors from the jdbc2
tests:
[mkdir] Created
dir: /home/maciek/git/copy-merge/jdbc-upstream/build/testresults
[junit] Testsuite: org.postgresql.test.jdbc2.Jdbc2TestSuite
[junit] Tests run: 269, Failures: 0, Errors: 131, Time elapsed:
13.212 sec
.......
.......
[junit] Test org.postgresql.test.jdbc2.Jdbc2TestSuite FAILED
[junit] Testsuite:
org.postgresql.test.jdbc2.optional.OptionalTestSuite
[junit] Tests run: 40, Failures: 0, Errors: 0, Time elapsed: 2.404
sec
[junit]
[junit] Testsuite: org.postgresql.test.jdbc3.Jdbc3TestSuite
[junit] Tests run: 65, Failures: 0, Errors: 0, Time elapsed: 2.048
sec
[junit]
[junit] Testsuite: org.postgresql.test.xa.XATestSuite
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.517
sec
[junit]
The initial Exception that seems to bork the Connection and trigger a
cascade of Exceptions is here:
[junit] Testcase:
testComments(org.postgresql.test.jdbc2.PreparedStatementTest): Caused
an ERROR
[junit] An I/O error occured while sending to the backend.
[junit] org.postgresql.util.PSQLException: An I/O error occured
while sending to the backend.
[junit] at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:220)
[junit] at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
[junit] at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
[junit] at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:360)
[junit] at
org.postgresql.test.jdbc2.PreparedStatementTest.testComments(PreparedStatementTest.java:437)
[junit] Caused by: java.io.EOFException
[junit] at
org.postgresql.core.PGStream.ReceiveChar(PGStream.java:261)
[junit] at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1183)
[junit] at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:194)
[junit]
Any thoughts? I grabbed this at trunk at this commit:
Author: jurka <jurka>
Date: Thu Mar 12 03:59:50 2009 +0000
Don't use pg_attrdef.adsrc to display a column's default value.
This can get out of date when dependent objects are renamed.
Instead decompile the adbin column to fetch up to date information.
Per complaint from Dickson S. Guedes and suggestion from Tom Lane
for the fix.
Thanks,
--
Maciek Sakrejda
Truviso, Inc.
http://www.truviso.com
On Mon, 23 Mar 2009, Maciek Sakrejda wrote: > (re-sending this--I tried yesterday but it looks like it failed without > a clear reason) Possibly you hit the size limit, this list only allows messages < 30k. > I've finally gotten the COPY functionality merge to a stable point and > wanted to run through the test suite, but I found that (even without > applying the COPY changes) I get a number of errors from the jdbc2 > tests: That's odd, it works for me. The cascading failure scenario can be seen when you end up crashing the server so future tests can't connect until the server restarts. Look in the server log to see what it has to say. Kris Jurka
Nothing suspicious in the logs (there are ERROR-level messages, but it looks like these are coming from negative tests). I rebuilt postgres and things seem to pass now, so maybe this was just an issue for that particular version. I *can* consistently reproduce it with that version though--it's something I can look into, but I guess it's not interfering with the COPY testing. I'll merge in a few more fixes (mostly encoding-related) that we've added at Truviso, and I hope to post a patch and pick up the discussion on COPY later this week. Thanks, and sorry about the confusion. -- Maciek Sakrejda Truviso, Inc. http://www.truviso.com -----Original Message----- From: Kris Jurka <books@ejurka.com> To: Maciek Sakrejda <msakrejda@truviso.com> Cc: pgsql-jdbc@postgresql.org Subject: Re: [JDBC] Test suite failures? Date: Mon, 23 Mar 2009 13:54:29 -0400 (EDT) On Mon, 23 Mar 2009, Maciek Sakrejda wrote: > (re-sending this--I tried yesterday but it looks like it failed without > a clear reason) Possibly you hit the size limit, this list only allows messages < 30k. > I've finally gotten the COPY functionality merge to a stable point and > wanted to run through the test suite, but I found that (even without > applying the COPY changes) I get a number of errors from the jdbc2 > tests: That's odd, it works for me. The cascading failure scenario can be seen when you end up crashing the server so future tests can't connect until the server restarts. Look in the server log to see what it has to say. Kris Jurka
Just to clarify--note that by 'version', I mean a particular revision of trunk--this is not a release build. -----Original Message----- From: Maciek Sakrejda <msakrejda@truviso.com> To: Kris Jurka <books@ejurka.com> Cc: pgsql-jdbc@postgresql.org Subject: Re: [JDBC] Test suite failures? Date: Mon, 23 Mar 2009 13:09:15 -0700 Nothing suspicious in the logs (there are ERROR-level messages, but it looks like these are coming from negative tests). I rebuilt postgres and things seem to pass now, so maybe this was just an issue for that particular version. I *can* consistently reproduce it with that version though--it's something I can look into, but I guess it's not interfering with the COPY testing. I'll merge in a few more fixes (mostly encoding-related) that we've added at Truviso, and I hope to post a patch and pick up the discussion on COPY later this week. Thanks, and sorry about the confusion. -- Maciek Sakrejda Truviso, Inc. http://www.truviso.com -----Original Message----- From: Kris Jurka <books@ejurka.com> To: Maciek Sakrejda <msakrejda@truviso.com> Cc: pgsql-jdbc@postgresql.org Subject: Re: [JDBC] Test suite failures? Date: Mon, 23 Mar 2009 13:54:29 -0400 (EDT) On Mon, 23 Mar 2009, Maciek Sakrejda wrote: > (re-sending this--I tried yesterday but it looks like it failed without > a clear reason) Possibly you hit the size limit, this list only allows messages < 30k. > I've finally gotten the COPY functionality merge to a stable point and > wanted to run through the test suite, but I found that (even without > applying the COPY changes) I get a number of errors from the jdbc2 > tests: That's odd, it works for me. The cascading failure scenario can be seen when you end up crashing the server so future tests can't connect until the server restarts. Look in the server log to see what it has to say. Kris Jurka