Hello Torben,

Sorry for my late response. Picking up after a holiday.
The oracle online tests are not so straight-forward to set up.
 Can I be of any assistance or have you sorted it out in the meantime?

Regards
Niels

On 24-04-15 01:50, Torben Barsballe wrote:
Excellent, good to know we are making progress.
When I go through and update the documentation, I'll make these points a bit more clear, rather than just showing up as an example.

SC4O hasn't been added yet, so I think that is why you are seeing that error.

Torben

On Thu, Apr 23, 2015 at 4:15 PM, Ben Caradoc-Davies <[email protected] <mailto:[email protected]>> wrote:

    Aha!

    Oh, this sucks horribly, but the good news is that I had a peek
    into the Jenkins pre-build script and I can reproduce the failures
    locally against my own database and I think I have fixed them for you:

    (1) For both database types, both "password" and "passwd" are
    required. I have added "passwd" which was missing. Yes, different
    fixtures look for different keys (*thunch* (sound of forehead
    hitting keyboard)), so having only one will cause only some to
    fail. Similar brain damage can be found in GeoTools. The
    documentation, while appearing to contain a bizarre duplication,
    is in fact correct!

    (2) Postgis tests appear to *require* dbtype=postgisng, and do not
    work with dbtype=postgis or this key not present, which is also
    curious. Probably a dodgy assumption somewhere, or need for
    consistency with mapping files which contain this alternative name
    (connection pooling, perhaps?). I have added dbtype=postgis to the
    Jenkins pre-build script. This second bizarre detail in the
    documentation is also correct!

    I have applied these two changes to Jenkins and have kicked the
    build. Fingers crossed.

    Kind regards,
    Ben.


    On 24/04/15 10:35, Torben Barsballe wrote:

        I took a look the actuall test script
        (Oracle_Data_ref_set.sql) extracted
        from the test data jar, and it references the TESTTBS tablespace
        frequently, without ever creating it, so it seems like an
        undocumented
        requirement. I'll try and get that tablespace added to the
        Oracle DB.

        I've added -DquietTests=false to the mvn command. Based on the
        test
        failures it look like data is missing somewhere, but I can't
        see any log
        messages suggesting why this might be occuring.


            - Are you able to run the tests in Eclipse against the
            same database? This
            might give you console output that surefire does not capture.

            No, the test databases are firewalled to be accessible
            from ares only. I

        have very limited access to them.

        Torben


-- Ben Caradoc-Davies <[email protected] <mailto:[email protected]>>
    Director
    Transient Software Limited <http://transient.nz/>
    New Zealand




------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to