From: Andrea A. <aa...@op...> - 2006-12-22 08:57:16
|
Jody Garnett ha scritto: > Justin we did have some kind of jalopy, svn problem here so "svn up" got > conflicts. Moving on .. to online tests. > > Great work on the devel guide page, we can start to remove the maven 1 > instructions now. > >> SEVERE: Could not obtain DBInfo object >> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.172 >> sec <<< FAILURE! > This is my first failure, in the PostGIS module. Ah, this is my fault. I did commit a change to the fixture.properties file without noticing while forward porting a bug fix from 2.2.x and it was pointing to a local postgis install instead of the one on refractions. I did revert my change. On a general note, it would be nice to have a way to override that does not require changing files on version control (I'll try to be more accurate, but I know myself, it will last a week and then I'll fall back on screwing up...). As a separate note, me hitting the refractions server is really unworkable, some on the test methods take minutes to run, and eventually fail timing out so I'm unable to run mvn install -Ponline anyways. For example, attached is what I get when I run the PostgisWithoutGeosOnlineTest, something I can't run on my local PC because I do not have an install of postgis without Geos (don't even know how to make one...). To give you a better idea, here is what "mvn install -Ponline" against the sole postgis module tells me when run against the refractions servers: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.geotools.data.postgis.PostgisDBInfoOnlineTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.906 sec Running org.geotools.filter.SQLEncoderPostgisTest WHERE ("gid" = '345')|WHERE (gid = '345') Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.344 sec Running org.geotools.filter.SQLEncoderPostgisGeosTest WHERE ("gid" = '345')|WHERE (gid = '345') Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.156 sec Running org.geotools.data.postgis.PostgisWithoutGeosOnlineTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 83.829 sec <<< FAILURE! Running org.geotools.data.postgis.PostgisPermissionOnlineTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 99 sec Running org.geotools.data.postgis.PostgisFeatureReaderOnlineTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 117.39 sec Running org.geotools.data.postgis.PostgisFeatureWriterOnlineTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 49.344 sec Running org.geotools.data.postgis.PostgisDataStoreAPIOnlineTest Tests run: 37, Failures: 0, Errors: 28, Skipped: 0, Time elapsed: 926.953 sec <<< FAILURE! Running org.geotools.data.postgis.collection.PostgisFeatureCollectionOnlineTest ... and then I killed it, it already used more than 20 minutes and postgis datastore api online test all failed due to table creation issues that I can't reproduce on my local postgis... here is an excerpt of failures: ------------------------------------------------------------------------------- Test set: org.geotools.data.postgis.PostgisDataStoreAPIOnlineTest ------------------------------------------------------------------------------- Tests run: 37, Failures: 0, Errors: 28, Skipped: 0, Time elapsed: 926.937 sec <<< FAILURE! testGetFeatureTypes(org.geotools.data.postgis.PostgisDataStoreAPIOnlineTest) Time elapsed: 6.172 sec <<< ERROR! org.postgresql.util.PSQLException: ERROR: duplicate key violates unique constraint "pg_class_relname_nsp_index" at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1525) ... org.geotools.data.postgis.AbstractPostgisDataTestCase.setUpRoadTable(AbstractPostgisDataTestCase.java:176) at org.geotools.data.postgis.AbstractPostgisDataTestCase.setupDbTables(AbstractPostgisDataTestCase.java:74) at ... testGetSchemaRoad(org.geotools.data.postgis.PostgisDataStoreAPIOnlineTest) Time elapsed: 44.062 sec <<< ERROR! org.postgresql.util.PSQLException: ERROR: relation "road" already exists at ... org.geotools.data.postgis.AbstractPostgisDataTestCase.setUpRoadTable(AbstractPostgisDataTestCase.java:176) at org.geotools.data.postgis.AbstractPostgisDataTestCase.setupDbTables(AbstractPostgisDataTestCase.java:74) at and so on... so it took more than 15 minutes to to try and fail to do the setUp() phase of the tests... Cheers Andrea |