Hi,

These tests fail some time :) Usually reason is that test expected to
have n open or closed connections, but encountered m. And number m
highly depends on environment (don't ask me why), which makes it hard
to debug them.

Best regards,
Roman Rokytskyy

--- In Firebird-Java@y..., "Rick Fincher" <rnf@t...> wrote:
> Hi All,
>
> In case you don't already know, the cvs sources from today produced
the
> following test failures when compiling under Windows 2000 sp3.
>
> [junit] Running org.firebirdsql.jca.TestPoolingConnectionManager
> [junit] Tests run: 4, Failures: 2, Errors: 0, Time elapsed: 19.318
sec
> [junit] TEST org.firebirdsql.jca.TestPoolingConnectionManager
FAILED
>
> [junit] Running org.firebirdsql.jdbc.TestFBWrappingDataSource
> [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 8.472
sec
> [junit] TEST org.firebirdsql.jdbc.TestFBWrappingDataSource FAILED
>
>
> tests-report-html:
> [junitreport] Using Xalan version: Xalan Java 2.2.D11
> [junitreport] Transform time: 7070ms
>
> ----- Original Message -----
>
> > Hello
> >
> > Finally I think I solve the problems that we have with
> time/date/timestamp with millisecond precisions and the difference
> > between JDK 1.3 and JDK 1.4 in timestamps. I commit it to the CVS.
> >
> > The changes was tested with internal tests with jdk 1.3.1 and
jdk
> 1.4.1 and seems to work OK. The change implies only XSQLVAR
> > encode/decode methods.
> >
> > Please test the changes.
> >
> > Regards
> > Blas Rodriguez Somoza