From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Test suite fails on non-default configuration |
Date: | 2011-04-18 21:28:27 |
Message-ID: | 4DAC66AB020000250003C97F@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
I just built a new jar file from a checkout of CVS HEAD, and (after
fixing up the UNICODE versus UTF8 issue) the unit tests still failed
on me:
runtest:
[junit] Testsuite: org.postgresql.test.jdbc2.Jdbc2TestSuite
[junit] Tests run: 293, Failures: 1, Errors: 0, Time elapsed:
35.78 sec
[junit]
[junit] Testcase:
testTransactionIsolation(org.postgresql.test.jdbc2.ConnectionTest):
FAILED
[junit] expected:<2> but was:<8>
[junit] junit.framework.AssertionFailedError: expected:<2> but
was:<8>
[junit] at
org.postgresql.test.jdbc2.ConnectionTest.testTransactionIsolation(
ConnectionTest.java:210)
[junit]
[junit]
[junit] Test org.postgresql.test.jdbc2.Jdbc2TestSuite FAILED
The cause is that the cluster I was running against has a
non-default postgresql.conf file -- default_transaction_isolation is
set to serializable, which runs afoul of this:
public void testTransactionIsolation() throws Exception
{
con = TestUtil.openDB();
// PostgreSQL defaults to READ COMMITTED
assertEquals(Connection.TRANSACTION_READ_COMMITTED,
con.getTransactionIsolation());
Should the unit tests really be failing based on configuration
options?
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-18 23:12:49 | Re: Test suite fails on non-default configuration |
Previous Message | Mike Fowler | 2011-04-18 16:52:23 | Re: [JDBC] JDBC connections to 9.1 |