Bug#300753: Regression test results

[Markus Schaber]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5F2A3E38CDA5748A81AA1810
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Hi, Wolfgang,

Wolfgang Baer schrieb:

>> As the tests work fine when running against SUN and IBM jdks, I assume
>> that the generated postgresql.jar is correct, but the JVMs clearly have
>> some problems.
> 
> please use the latest vms in unstable as reference - as the ones in
> sarge are known to have several problems. Also the vms currently
> in unstable will be include in sarge (at least for sarge/sablevm).

Okay, I did so. I used update-alternatives to switch between the JDKs
and ran the following command line:

 CLASSPATH=/usr/share/java/junit-3.8.1.jar ant test -Dport=5432
-Ddatabase=jdbcdrivertest

The results for the regression tests:

gij-wrapper-4.0: looks slightly better than 3.X

>     [junit] Testsuite: org.postgresql.test.jdbc2.Jdbc2TestSuite
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
>     [junit] Test org.postgresql.test.jdbc2.Jdbc2TestSuite FAILED
> 
>     [junit] Testsuite: org.postgresql.test.jdbc2.optional.OptionalTestSuite
>     [junit] Tests run: 38, Failures: 0, Errors: 0, Time elapsed: 3,627 sec
> 
>     [junit] Testsuite: org.postgresql.test.jdbc3.Jdbc3TestSuite
>     [junit] Tests run: 42, Failures: 4, Errors: 1, Time elapsed: 4,265 sec
>     [junit] Test org.postgresql.test.jdbc3.Jdbc3TestSuite FAILED

sablevm 1.11.1:
>    runtest:
> 
>    BUILD FAILED
>    /leisure/chroots/kaffesarge/usr/src/libpgjava-7.4.2/src/interfaces/jdbc/build.xml:339: 
>    Could not create type junit due to ?/bin is not an absolute path
> 

jamvm 1.2.5: Seems not to run the tests at all, without any error
messages, but complaining that it does not find a tool.jar. It lists all
the targets as it executes them, but does not run any tests actually.

kaffe 1.1.4.PRECVS12-1: The same as jamvm.

DISCLAIMER: I did not have time to look into the details yet (maybe some
config / environment variables have to be adjusted).

Markus
-- 
Markus Schaber - http://schabi.de/

But hey!, Standard compliance is something we should strive for, so
let's try and change the Standard :-) [Alexandre Oliva, GCC Developer]

--------------enig5F2A3E38CDA5748A81AA1810
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD4DBQFCS+OQ6IhVmcufrl4RA/fHAJdMBtTA/d7WqaMIlBRP0ZHwGUFSAJ9+6b/j
Ue9pgnq5ApMy7bTSxcr22g==
=0FTo
-----END PGP SIGNATURE-----

--------------enig5F2A3E38CDA5748A81AA1810--