Re: Test suite failures?

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(at)truviso(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)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(at)ejurka(dot)com>
To: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)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