Andrea figured out the issue in the GeoServer meeting today - turns out
that when I was getting the cite tests working on the new build server last
week, the port number in /forms got changed. This is now fixed, and the
ares cite tests are working again (except for wfs-1.1, which is expected).
I have re-enabled all the jobs for now.
This might also be related to the failures on apollo, as I expect /forms
also needs updating there. Looking into that now.
Torben
On Mon, Oct 16, 2017 at 5:37 PM, Ben Caradoc-Davies <[email protected]>
wrote:
> Torben,
>
> it looks to me like the test engine is running before GeoServer is up:
> https://build.geoserver.org/job/cite-wfs-1.1/1502/consoleText
>
> I think the up-ness test is bad and tests only worked on ares because it
> was a slower machine and took time to build the suite. The test failure
> occurs before GeoServer is accepting connections. curl is probably
> successfully retrieving a Jetty error page.
>
> Kind regards,
> Ben.
>
> On 17/10/17 12:33, Torben Barsballe wrote:
>
>> With regards to the build.geoserver.org cite tests, we are a lot further
>> along then we are before, but have run up against a failure coming out of
>> the cite engine. If anyone more familiar with the cite tests could
>> comment,
>> that would be appreciated.
>>
>
> --
> Ben Caradoc-Davies <[email protected]>
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
