[Geoserver-devel] Build failed in Hudson: cite-wms-1.1-trunk #136

See <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/&gt;

------------------------------------------
[...truncated 1147 lines...]
         VAR_SIZE_1: 188
      Test wms:wmsops-getfeatureinfo-params-feature_count-2 Passed
      Testing wms:wmsops-getfeatureinfo-params-info_format-1 (wms-1.1.1/d39e1812_1)...
         Assertion: When the INFO_FORMAT parameter is missing, then the Content-type header returned is one of the formats advertised.
         VAR_DEFAULT_INFO_FORMAT: text/plain
      Test wms:wmsops-getfeatureinfo-params-info_format-1 Passed
      Testing wms:wmsops-getfeatureinfo-params-info_format-2 (wms-1.1.1/d39e1828_1)...
         Assertion: When the INFO_FORMAT parameter is application/vnd.ogc.gml, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-params-info_format-2 Passed
      Testing wms:wmsops-getfeatureinfo-params-info_format-3 (wms-1.1.1/d39e1842_1)...
         Assertion: When the INFO_FORMAT parameter is application/vnd.ogc.gml, then the response validates with the Galdos GML instance document validator.
      Test wms:wmsops-getfeatureinfo-params-info_format-3 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-1 (wms-1.1.1/d39e1856_1)...
         Assertion: When a GetFeatureInfo request contains a single layer, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-1 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-2 (wms-1.1.1/d39e1872_1)...
         Assertion: When a GetFeatureInfo request contains two layers, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-2 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-3 (wms-1.1.1/d39e1892_1)...
         Assertion: When a GetFeatureInfo request contains three layers, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-3 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-4 (wms-1.1.1/d39e1913_1)...
         Assertion: When a GetFeatureInfo request contains fewer layers in the QUERY_LAYERS parameter than it does in the LAYERS parameter, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-4 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-5 (wms-1.1.1/d39e1934_1)...
         Assertion: When a layer requested is not contained in the Capabilities XML of the WMS, then the server issues a Service Exception.
      Test wms:wmsops-getfeatureinfo-params-query_layers-5 Passed
      Testing wms:wmsops-getmap-params-bbox-10 (wms-1.1.1/d39e1966_1)...
         Assertion: When a request contains a Bounding Box with y values that are beyond 90 degrees, then the server returns empty content for the area beyond 90 degrees.
      Test wms:wmsops-getmap-params-bbox-10 Passed
      Testing wms:wmsops-getmap-params-bbox-3 (wms-1.1.1/d39e2009_1)...
         Assertion: When a GetMap request uses scientific notation values for the BBOX parameter, then the response is valid.
         VAR_CHECKSUM_1: 3138646246
      Test wms:wmsops-getmap-params-bbox-3 Passed
      Testing wms:wmsops-getmap-params-bbox-4 (wms-1.1.1/d39e2038_1)...
         Assertion: The server interprets the bounding box as going around the "outside" of the pixels of the image rather than through the centers of the border pixels.
      Test wms:wmsops-getmap-params-bbox-4 Passed
      Testing wms:wmsops-getmap-params-bbox-5 (wms-1.1.1/d39e2052_1)...
         Assertion: When the BBOX parameter's minimum X is greater than the maximum X, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-5 Passed
      Testing wms:wmsops-getmap-params-bbox-6 (wms-1.1.1/d39e2066_1)...
         Assertion: When the BBOX parameter's minimum X is equal to the maximum X, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-6 Passed
      Testing wms:wmsops-getmap-params-bbox-7 (wms-1.1.1/d39e2080_1)...
         Assertion: When the BBOX parameter's minimum Y is greater than the maximum Y, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-7 Passed
      Testing wms:wmsops-getmap-params-bbox-8 (wms-1.1.1/d39e2095_1)...
         Assertion: When the BBOX parameter's minimum Y is equal to the maximum Y, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-8 Passed
      Testing wms:wmsops-getmap-params-bbox-9 (wms-1.1.1/d39e2109_1)...
         Assertion: When a request contains a Bounding Box whose area does not overlap at all with the BoundingBox advertised, then the server returns empty content.
      Test wms:wmsops-getmap-params-bbox-9 Passed
      Testing wms:wmsops-getmap-params-bgcolor-1 (wms-1.1.1/d39e2123_1)...
         Assertion: When a GetMap request is made with no BGCOLOR parameter, then areas which are not covered contain white (0xFFFFFF) pixels.
      Test wms:wmsops-getmap-params-bgcolor-1 Passed
      Testing wms:wmsops-getmap-params-bgcolor-2 (wms-1.1.1/d39e2137_1)...
         Assertion: When a GetMap request is made with a BGCOLOR parameter, then areas which are not covered are set to the value of BGCOLOR.
      Test wms:wmsops-getmap-params-bgcolor-2 Passed
      Testing wms:wmsops-getmap-params-exceptions-1 (wms-1.1.1/d39e2149_1)...
         Assertion: When an exception is raised without specifying the EXCEPTIONS parameter, then the Content-type of the return header is application/vnd.ogc.se_xml.
      Test wms:wmsops-getmap-params-exceptions-1 Passed
      Testing wms:wmsops-getmap-params-exceptions-2 (wms-1.1.1/d39e2158_1)...
         Assertion: When an exception is raised and EXCEPTIONS=application/vnd.ogc.se_xml, then the Content-type of the return header is application/vnd.ogc.se_xml.
      Test wms:wmsops-getmap-params-exceptions-2 Passed
      Testing wms:wmsops-getmap-params-exceptions-4 (wms-1.1.1/d39e2170_1)...
         Assertion: When an exception is raised and EXCEPTIONS=application/vnd.ogc.se_inimage, then the Content-type of the return header is the same as the FORMAT requested.
      Test wms:wmsops-getmap-params-exceptions-4 Passed
      Testing wms:wmsops-getmap-params-format-1 (wms-1.1.1/d39e2218_1)...
         Assertion: When a GetMap request contains a Format that is not advertised, then the server throws a Service Exception (code="InvalidFormat").
      Test wms:wmsops-getmap-params-format-1 Passed
      Testing wms:wmsops-getmap-params-format-2 (wms-1.1.1/d39e2230_1)...
         Assertion: When a GetMap request is made using format=image/gif, then the response is a valid gif.
         VAR_IMAGE_TYPE: gif
      Test wms:wmsops-getmap-params-format-2 Passed
      Testing wms:wmsops-getmap-params-format-3 (wms-1.1.1/d39e2243_1)...
         Assertion: When a GetMap request is made using format=image/jpeg, then the response is a valid jpeg.
         VAR_IMAGE_TYPE: jpeg
      Test wms:wmsops-getmap-params-format-3 Passed
      Testing wms:wmsops-getmap-params-format-4 (wms-1.1.1/d39e2255_1)...
         Assertion: When a GetMap request is made using format=image/png, then the response is a valid png.
         VAR_IMAGE_TYPE: png
      Test wms:wmsops-getmap-params-format-4 Passed
      Testing wms:wmsops-getmap-params-layers-1 (wms-1.1.1/d39e2267_1)...
         Assertion: When a GetMap request contains a single layer name, then the response is valid.
      Test wms:wmsops-getmap-params-layers-1 Passed
      Testing wms:wmsops-getmap-params-layers-2 (wms-1.1.1/d39e2281_1)...
         Assertion: When a GetMap request contains two layer names (separated by a comma), then the response is valid.
      Test wms:wmsops-getmap-params-layers-2 Passed
      Testing wms:wmsops-getmap-params-layers-3 (wms-1.1.1/d39e2297_1)...
         Assertion: When a GetMap request contains three layer names (separated by commas), then the response is valid.
      Test wms:wmsops-getmap-params-layers-3 Passed
      Testing wms:wmsops-getmap-params-layers-5 (wms-1.1.1/d39e2314_1)...
         Assertion: When the layer in a GetMap request is invalid, then the response is an exception (code="LayerNotDefined").
      Test wms:wmsops-getmap-params-layers-5 Passed
      Testing wms:wmsops-getmap-params-layers-6 (wms-1.1.1/d39e2326_1)...
         Assertion: When a GetMap request contains two layers where the first is valid and the second is invalid, then the response is an exception (code="LayerNotDefined").
      Test wms:wmsops-getmap-params-layers-6 Passed
      Testing wms:wmsops-getmap-params-layers-7 (wms-1.1.1/d39e2340_1)...
         Assertion: When a GetMap request contains two layers where the first is invalid and the second is valid, then the response is an exception (code="LayerNotDefined").
      Test wms:wmsops-getmap-params-layers-7 Passed
      Testing wms:wmsops-getmap-params-request-1 (wms-1.1.1/d39e2354_1)...
         Assertion: When a GetMap request is made using REQUEST=map instead of REQUEST=GetMap, the response is valid.
      Test wms:wmsops-getmap-params-request-1 Passed
      Testing wms:wmsops-getmap-params-srs-1 (wms-1.1.1/d39e2368_1)...
         Assertion: When a GetMap request contains a single layer and a SRS where the SRS is contained directly in the layer in the capabilities document, then the response is valid.
      Test wms:wmsops-getmap-params-srs-1 Passed
      Testing wms:wmsops-getmap-params-srs-3 (wms-1.1.1/d39e2396_1)...
         Assertion: When the SRS parameter in a GetMap request contains a SRS that is not valid for any of the layers being requested, then the server shall throw a Service Exception (code = "InvalidSRS").
      Test wms:wmsops-getmap-params-srs-3 Passed
      Testing wms:wmsops-getmap-params-styles-1 (wms-1.1.1/d39e2411_1)...
         Assertion: When a GetMap request contains a single layer and a single style where the style is contained directly in the layer in the capabilities document, then the response is valid.
      Test wms:wmsops-getmap-params-styles-1 Passed
      Testing wms:wmsops-getmap-params-styles-10 (wms-1.1.1/d39e2427_1)...
         Assertion: When a GetMap request contains two layers, where one of the styles is valid and one is not, then the response is an exception (code=StyleNotDefined).
      Test wms:wmsops-getmap-params-styles-10 Passed
      Testing wms:wmsops-getmap-params-styles-3 (wms-1.1.1/d39e2462_1)...
         Assertion: When a GetMap request contains two layers and two styles (separated by a comma), then the response is valid.
      Test wms:wmsops-getmap-params-styles-3 Passed
      Testing wms:wmsops-getmap-params-styles-4 (wms-1.1.1/d39e2478_1)...
         Assertion: When a GetMap request contains three layers and three styles (separated by commas), then the response is valid.
      Test wms:wmsops-getmap-params-styles-4 Passed
      Testing wms:wmsops-getmap-params-styles-5 (wms-1.1.1/d39e2494_1)...
         Assertion: When a GetMap request contains an unadvertised Style, then the response is an exception (code=StyleNotDefined).
      Test wms:wmsops-getmap-params-styles-5 Passed
      Testing wms:wmsops-getmap-params-styles-6 (wms-1.1.1/d39e2509_1)...
         Assertion: When a GetMap request contains a single layer and a null style value (as in "STYLES="), then the response is valid.
      Test wms:wmsops-getmap-params-styles-6 Passed
      Testing wms:wmsops-getmap-params-styles-7 (wms-1.1.1/d39e2523_1)...
         Assertion: When a GetMap request contains multiple layers and a mixture of named and default styles (as in "STYLES=style1,style2,"), then the response is valid.
      Test wms:wmsops-getmap-params-styles-7 Passed
      Testing wms:wmsops-getmap-params-styles-8 (wms-1.1.1/d39e2546_1)...
         Assertion: When a GetMap request contains multiple layers and requests all layers to be shown in the default style by using null values between commas (as in "STYLES=,"), then the response is valid.
      Test wms:wmsops-getmap-params-styles-8 Passed
      Testing wms:wmsops-getmap-params-styles-9 (wms-1.1.1/d39e2567_1)...
         Assertion: When a GetMap request contains multiple layers and requests all layers to be shown in the default style by using a single null value (as in "STYLES="), then the response is valid.
      Test wms:wmsops-getmap-params-styles-9 Passed
      Testing wms:wmsops-getmap-params-transparent-1 (wms-1.1.1/d39e2588_1)...
         Assertion: When a GetMap request is made with no TRANSPARENT parameter and a FORMAT that supports transparency over a BBOX that is not completely covered, then the response contains no transparent pixels.
      Test wms:wmsops-getmap-params-transparent-1 Passed
      Testing wms:wmsops-getmap-params-transparent-2 (wms-1.1.1/d39e2602_1)...
         Assertion: When a GetMap request is made with TRANSPARENT=fAlSe and a FORMAT that supports transparency over a BBOX that is not completely covered, then the response contains no transparent pixels.
      Test wms:wmsops-getmap-params-transparent-2 Passed
      Testing wms:wmsops-getmap-params-transparent-3 (wms-1.1.1/d39e2617_1)...
         Assertion: When a GetMap request is made with TRANSPARENT=TRUE and a FORMAT that supports transparency over a BBOX that is not completely covered, then the response contains transparent pixels.
      Test wms:wmsops-getmap-params-transparent-3 Passed
      Testing wms:wmsops-getmap-params-version-1 (wms-1.1.1/d39e2631_1)...
         Assertion: When a GetMap request is made using WMTVER instead of VERSION, the response is valid.
      Test wms:wmsops-getmap-params-version-1 Passed
      Testing wms:wmsops-getmap-params-width_height-1 (wms-1.1.1/d39e2645_1)...
         Assertion: When a request is made with WIDTH=1024 and HEIGHT=768, the image returned is exactly the size requested.
      Test wms:wmsops-getmap-params-width_height-1 Passed
      Testing wms:wmsops-getmap-params-width_height-2 (wms-1.1.1/d39e2664_1)...
         Assertion: When a request is made with WIDTH=16 and HEIGHT=16, the image returned is exactly the size requested.
      Test wms:wmsops-getmap-params-width_height-2 Passed
      Testing wms:wmsops-getfeatureinfo-each-info_format (wms-1.1.1/d39e2680_1)...
         Assertion: For each advertised GetFeatureInfo format, when a GetFeatureInfo request is made with the INFO_FORMAT parameter set to the format, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-each-info_format Passed
      Testing wms:wmsops-getfeatureinfo-each-info_format (wms-1.1.1/d39e2680_2)...
         Assertion: For each advertised GetFeatureInfo format, when a GetFeatureInfo request is made with the INFO_FORMAT parameter set to the format, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-each-info_format Passed
      Testing wms:wmsops-getfeatureinfo-each-info_format (wms-1.1.1/d39e2680_3)...
         Assertion: For each advertised GetFeatureInfo format, when a GetFeatureInfo request is made with the INFO_FORMAT parameter set to the format, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-each-info_format Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_1)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_2)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_3)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_4)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_5)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_6)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_7)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_8)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_9)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_10)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_11)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_1)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_2)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_3)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_4)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_5)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_6)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_7)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_8)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_9)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_10)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_11)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-srs (wms-1.1.1/d39e2711_1)...
         Assertion: For each SRS in the capabilities document, when a GetMap request uses the SRS, then the response is valid.
      Test wms:wmsops-getmap-each-srs Passed
      Testing wms:wmsops-getmap-layer-encoded-name (wms-1.1.1/d39e2739_1)...
         Assertion: When a layer is requested using encoded characters in its name, the response is a map.
      Test wms:wmsops-getmap-layer-encoded-name Passed
      Testing wms:basic_elements-validate-exception (wms-1.1.1/d39e2745_1)...
         Assertion: When an exception is generated, it validates.
      Test wms:basic_elements-validate-exception Passed
   Test wms:main Failed (Inherited failure)
Suite wms:main_wms Failed
<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools&gt;
cp target/sessions/session.xml.wms-1.1.1 users/geoserver/wms-1.1.1/session.xml
Test wms:main (wms-1.1.1) Failed (Inherited Failure)
   Test wms:wmsops-getcapabilities-response-2 (wms-1.1.1/d39e1639_1) Failed
RETURN=1
Pinging GeoServer at http://localhost:11010/geoserver

curl: (7) couldn't connect to host
GeoServer is offline

CITE WMS 1.1.1 is failing du

On Wed, 2011-01-05 at 06:47 +0000, Hudson wrote:

See <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/&gt;

------------------------------------------
[...truncated 1147 lines...]
         VAR_SIZE_1: 188

I fixed the cite failure I recognized as my fault (empty
VendorSpecificCapabilities), but now when I run it locally it the
following assertion fails:

<quote>
Test wms:wmsops-getcapabilities-params-request-1 (wms-1.1.1/d40e1042_1)

Assertion: When REQUEST is &quot;capabilities&quot;, then the response
is capabilities XML.

Request d40e3116_1:
   Method: get
   URL:
http://localhost:9090/geoserver/wms?SERVICE=WMS&&SeRvIcE=WMS&ReQuEsT=capabilities
   Response from parser ::
      <WMS_Capabilities xmlns="http://www.opengis.net/wms&quot;
</quote>

Now, the capabilities URL I gave to the test engine has the
version=1.1.1 parameter, not sure why the engine is trying the above
request without version parameter, and hence the failure is due to the
WMS 1.3 getcaps being returned instead of the 1.1.1 ones.

Any clue?

Cheers,
Gabriel

On Wed, 2011-01-05 at 06:47 +0000, Hudson wrote:

See <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/&gt;

------------------------------------------
[...truncated 1147 lines...]

...

   Test wms:main Failed (Inherited failure)
Suite wms:main_wms Failed
<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools&gt;
cp target/sessions/session.xml.wms-1.1.1 users/geoserver/wms-1.1.1/session.xml
Test wms:main (wms-1.1.1) Failed (Inherited Failure)
   Test wms:wmsops-getcapabilities-response-2 (wms-1.1.1/d39e1639_1) Failed
RETURN=1
Pinging GeoServer at http://localhost:11010/geoserver

curl: (7) couldn't connect to host
GeoServer is offline

Hmmm… what version of the tests are you running?

I just looked at the sources of those tests and it looks like the WMTVER rather than VERSION parameter should be used. But it does not look like it with the url you posted in. Are you positive that is the url being requested?

On Wed, Jan 5, 2011 at 9:42 AM, Gabriel Roldán <groldan@anonymised.com.1501…> wrote:

I fixed the cite failure I recognized as my fault (empty
VendorSpecificCapabilities), but now when I run it locally it the
following assertion fails:

Test wms:wmsops-getcapabilities-params-request-1 (wms-1.1.1/d40e1042_1)

Assertion: When REQUEST is "capabilities", then the response
is capabilities XML.

Request d40e3116_1:
Method: get
URL:
http://localhost:9090/geoserver/wms?SERVICE=WMS&&SeRvIcE=WMS&ReQuEsT=capabilities
Response from parser ::
<WMS_Capabilities xmlns=“http://www.opengis.net/wms

Now, the capabilities URL I gave to the test engine has the
version=1.1.1 parameter, not sure why the engine is trying the above
request without version parameter, and hence the failure is due to the
WMS 1.3 getcaps being returned instead of the 1.1.1 ones.

Any clue?

Cheers,
Gabriel

On Wed, 2011-01-05 at 06:47 +0000, Hudson wrote:

See <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/>


[…truncated 1147 lines…]

Test wms:main Failed (Inherited failure)
Suite wms:main_wms Failed
<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools>
cp target/sessions/session.xml.wms-1.1.1 users/geoserver/wms-1.1.1/session.xml
Test wms:main (wms-1.1.1) Failed (Inherited Failure)
Test wms:wmsops-getcapabilities-response-2 (wms-1.1.1/d39e1639_1) Failed
RETURN=1
Pinging GeoServer at http://localhost:11010/geoserver

curl: (7) couldn’t connect to host
GeoServer is offline


Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

See <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/137/&gt;

------------------------------------------
[...truncated 1162 lines...]
         VAR_SIZE_1: 188
      Test wms:wmsops-getfeatureinfo-params-feature_count-2 Passed
      Testing wms:wmsops-getfeatureinfo-params-info_format-1 (wms-1.1.1/d39e1812_1)...
         Assertion: When the INFO_FORMAT parameter is missing, then the Content-type header returned is one of the formats advertised.
         VAR_DEFAULT_INFO_FORMAT: text/plain
      Test wms:wmsops-getfeatureinfo-params-info_format-1 Passed
      Testing wms:wmsops-getfeatureinfo-params-info_format-2 (wms-1.1.1/d39e1828_1)...
         Assertion: When the INFO_FORMAT parameter is application/vnd.ogc.gml, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-params-info_format-2 Passed
      Testing wms:wmsops-getfeatureinfo-params-info_format-3 (wms-1.1.1/d39e1842_1)...
         Assertion: When the INFO_FORMAT parameter is application/vnd.ogc.gml, then the response validates with the Galdos GML instance document validator.
      Test wms:wmsops-getfeatureinfo-params-info_format-3 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-1 (wms-1.1.1/d39e1856_1)...
         Assertion: When a GetFeatureInfo request contains a single layer, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-1 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-2 (wms-1.1.1/d39e1872_1)...
         Assertion: When a GetFeatureInfo request contains two layers, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-2 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-3 (wms-1.1.1/d39e1892_1)...
         Assertion: When a GetFeatureInfo request contains three layers, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-3 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-4 (wms-1.1.1/d39e1913_1)...
         Assertion: When a GetFeatureInfo request contains fewer layers in the QUERY_LAYERS parameter than it does in the LAYERS parameter, then the response is valid.
      Test wms:wmsops-getfeatureinfo-params-query_layers-4 Passed
      Testing wms:wmsops-getfeatureinfo-params-query_layers-5 (wms-1.1.1/d39e1934_1)...
         Assertion: When a layer requested is not contained in the Capabilities XML of the WMS, then the server issues a Service Exception.
      Test wms:wmsops-getfeatureinfo-params-query_layers-5 Passed
      Testing wms:wmsops-getmap-params-bbox-10 (wms-1.1.1/d39e1966_1)...
         Assertion: When a request contains a Bounding Box with y values that are beyond 90 degrees, then the server returns empty content for the area beyond 90 degrees.
      Test wms:wmsops-getmap-params-bbox-10 Passed
      Testing wms:wmsops-getmap-params-bbox-3 (wms-1.1.1/d39e2009_1)...
         Assertion: When a GetMap request uses scientific notation values for the BBOX parameter, then the response is valid.
         VAR_CHECKSUM_1: 3138646246
      Test wms:wmsops-getmap-params-bbox-3 Passed
      Testing wms:wmsops-getmap-params-bbox-4 (wms-1.1.1/d39e2038_1)...
         Assertion: The server interprets the bounding box as going around the "outside" of the pixels of the image rather than through the centers of the border pixels.
      Test wms:wmsops-getmap-params-bbox-4 Passed
      Testing wms:wmsops-getmap-params-bbox-5 (wms-1.1.1/d39e2052_1)...
         Assertion: When the BBOX parameter's minimum X is greater than the maximum X, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-5 Passed
      Testing wms:wmsops-getmap-params-bbox-6 (wms-1.1.1/d39e2066_1)...
         Assertion: When the BBOX parameter's minimum X is equal to the maximum X, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-6 Passed
      Testing wms:wmsops-getmap-params-bbox-7 (wms-1.1.1/d39e2080_1)...
         Assertion: When the BBOX parameter's minimum Y is greater than the maximum Y, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-7 Passed
      Testing wms:wmsops-getmap-params-bbox-8 (wms-1.1.1/d39e2095_1)...
         Assertion: When the BBOX parameter's minimum Y is equal to the maximum Y, then the server throws an exception.
      Test wms:wmsops-getmap-params-bbox-8 Passed
      Testing wms:wmsops-getmap-params-bbox-9 (wms-1.1.1/d39e2109_1)...
         Assertion: When a request contains a Bounding Box whose area does not overlap at all with the BoundingBox advertised, then the server returns empty content.
      Test wms:wmsops-getmap-params-bbox-9 Passed
      Testing wms:wmsops-getmap-params-bgcolor-1 (wms-1.1.1/d39e2123_1)...
         Assertion: When a GetMap request is made with no BGCOLOR parameter, then areas which are not covered contain white (0xFFFFFF) pixels.
      Test wms:wmsops-getmap-params-bgcolor-1 Passed
      Testing wms:wmsops-getmap-params-bgcolor-2 (wms-1.1.1/d39e2137_1)...
         Assertion: When a GetMap request is made with a BGCOLOR parameter, then areas which are not covered are set to the value of BGCOLOR.
      Test wms:wmsops-getmap-params-bgcolor-2 Passed
      Testing wms:wmsops-getmap-params-exceptions-1 (wms-1.1.1/d39e2149_1)...
         Assertion: When an exception is raised without specifying the EXCEPTIONS parameter, then the Content-type of the return header is application/vnd.ogc.se_xml.
      Test wms:wmsops-getmap-params-exceptions-1 Passed
      Testing wms:wmsops-getmap-params-exceptions-2 (wms-1.1.1/d39e2158_1)...
         Assertion: When an exception is raised and EXCEPTIONS=application/vnd.ogc.se_xml, then the Content-type of the return header is application/vnd.ogc.se_xml.
      Test wms:wmsops-getmap-params-exceptions-2 Passed
      Testing wms:wmsops-getmap-params-exceptions-4 (wms-1.1.1/d39e2170_1)...
         Assertion: When an exception is raised and EXCEPTIONS=application/vnd.ogc.se_inimage, then the Content-type of the return header is the same as the FORMAT requested.
      Test wms:wmsops-getmap-params-exceptions-4 Passed
      Testing wms:wmsops-getmap-params-format-1 (wms-1.1.1/d39e2218_1)...
         Assertion: When a GetMap request contains a Format that is not advertised, then the server throws a Service Exception (code="InvalidFormat").
      Test wms:wmsops-getmap-params-format-1 Passed
      Testing wms:wmsops-getmap-params-format-2 (wms-1.1.1/d39e2230_1)...
         Assertion: When a GetMap request is made using format=image/gif, then the response is a valid gif.
         VAR_IMAGE_TYPE: gif
      Test wms:wmsops-getmap-params-format-2 Passed
      Testing wms:wmsops-getmap-params-format-3 (wms-1.1.1/d39e2243_1)...
         Assertion: When a GetMap request is made using format=image/jpeg, then the response is a valid jpeg.
         VAR_IMAGE_TYPE: jpeg
      Test wms:wmsops-getmap-params-format-3 Passed
      Testing wms:wmsops-getmap-params-format-4 (wms-1.1.1/d39e2255_1)...
         Assertion: When a GetMap request is made using format=image/png, then the response is a valid png.
         VAR_IMAGE_TYPE: png
      Test wms:wmsops-getmap-params-format-4 Passed
      Testing wms:wmsops-getmap-params-layers-1 (wms-1.1.1/d39e2267_1)...
         Assertion: When a GetMap request contains a single layer name, then the response is valid.
      Test wms:wmsops-getmap-params-layers-1 Passed
      Testing wms:wmsops-getmap-params-layers-2 (wms-1.1.1/d39e2281_1)...
         Assertion: When a GetMap request contains two layer names (separated by a comma), then the response is valid.
      Test wms:wmsops-getmap-params-layers-2 Passed
      Testing wms:wmsops-getmap-params-layers-3 (wms-1.1.1/d39e2297_1)...
         Assertion: When a GetMap request contains three layer names (separated by commas), then the response is valid.
      Test wms:wmsops-getmap-params-layers-3 Passed
      Testing wms:wmsops-getmap-params-layers-5 (wms-1.1.1/d39e2314_1)...
         Assertion: When the layer in a GetMap request is invalid, then the response is an exception (code="LayerNotDefined").
      Test wms:wmsops-getmap-params-layers-5 Passed
      Testing wms:wmsops-getmap-params-layers-6 (wms-1.1.1/d39e2326_1)...
         Assertion: When a GetMap request contains two layers where the first is valid and the second is invalid, then the response is an exception (code="LayerNotDefined").
      Test wms:wmsops-getmap-params-layers-6 Passed
      Testing wms:wmsops-getmap-params-layers-7 (wms-1.1.1/d39e2340_1)...
         Assertion: When a GetMap request contains two layers where the first is invalid and the second is valid, then the response is an exception (code="LayerNotDefined").
      Test wms:wmsops-getmap-params-layers-7 Passed
      Testing wms:wmsops-getmap-params-request-1 (wms-1.1.1/d39e2354_1)...
         Assertion: When a GetMap request is made using REQUEST=map instead of REQUEST=GetMap, the response is valid.
      Test wms:wmsops-getmap-params-request-1 Passed
      Testing wms:wmsops-getmap-params-srs-1 (wms-1.1.1/d39e2368_1)...
         Assertion: When a GetMap request contains a single layer and a SRS where the SRS is contained directly in the layer in the capabilities document, then the response is valid.
      Test wms:wmsops-getmap-params-srs-1 Passed
      Testing wms:wmsops-getmap-params-srs-3 (wms-1.1.1/d39e2396_1)...
         Assertion: When the SRS parameter in a GetMap request contains a SRS that is not valid for any of the layers being requested, then the server shall throw a Service Exception (code = "InvalidSRS").
      Test wms:wmsops-getmap-params-srs-3 Passed
      Testing wms:wmsops-getmap-params-styles-1 (wms-1.1.1/d39e2411_1)...
         Assertion: When a GetMap request contains a single layer and a single style where the style is contained directly in the layer in the capabilities document, then the response is valid.
      Test wms:wmsops-getmap-params-styles-1 Passed
      Testing wms:wmsops-getmap-params-styles-10 (wms-1.1.1/d39e2427_1)...
         Assertion: When a GetMap request contains two layers, where one of the styles is valid and one is not, then the response is an exception (code=StyleNotDefined).
      Test wms:wmsops-getmap-params-styles-10 Passed
      Testing wms:wmsops-getmap-params-styles-3 (wms-1.1.1/d39e2462_1)...
         Assertion: When a GetMap request contains two layers and two styles (separated by a comma), then the response is valid.
      Test wms:wmsops-getmap-params-styles-3 Passed
      Testing wms:wmsops-getmap-params-styles-4 (wms-1.1.1/d39e2478_1)...
         Assertion: When a GetMap request contains three layers and three styles (separated by commas), then the response is valid.
      Test wms:wmsops-getmap-params-styles-4 Passed
      Testing wms:wmsops-getmap-params-styles-5 (wms-1.1.1/d39e2494_1)...
         Assertion: When a GetMap request contains an unadvertised Style, then the response is an exception (code=StyleNotDefined).
      Test wms:wmsops-getmap-params-styles-5 Passed
      Testing wms:wmsops-getmap-params-styles-6 (wms-1.1.1/d39e2509_1)...
         Assertion: When a GetMap request contains a single layer and a null style value (as in "STYLES="), then the response is valid.
      Test wms:wmsops-getmap-params-styles-6 Passed
      Testing wms:wmsops-getmap-params-styles-7 (wms-1.1.1/d39e2523_1)...
         Assertion: When a GetMap request contains multiple layers and a mixture of named and default styles (as in "STYLES=style1,style2,"), then the response is valid.
      Test wms:wmsops-getmap-params-styles-7 Passed
      Testing wms:wmsops-getmap-params-styles-8 (wms-1.1.1/d39e2546_1)...
         Assertion: When a GetMap request contains multiple layers and requests all layers to be shown in the default style by using null values between commas (as in "STYLES=,"), then the response is valid.
      Test wms:wmsops-getmap-params-styles-8 Passed
      Testing wms:wmsops-getmap-params-styles-9 (wms-1.1.1/d39e2567_1)...
         Assertion: When a GetMap request contains multiple layers and requests all layers to be shown in the default style by using a single null value (as in "STYLES="), then the response is valid.
      Test wms:wmsops-getmap-params-styles-9 Passed
      Testing wms:wmsops-getmap-params-transparent-1 (wms-1.1.1/d39e2588_1)...
         Assertion: When a GetMap request is made with no TRANSPARENT parameter and a FORMAT that supports transparency over a BBOX that is not completely covered, then the response contains no transparent pixels.
      Test wms:wmsops-getmap-params-transparent-1 Passed
      Testing wms:wmsops-getmap-params-transparent-2 (wms-1.1.1/d39e2602_1)...
         Assertion: When a GetMap request is made with TRANSPARENT=fAlSe and a FORMAT that supports transparency over a BBOX that is not completely covered, then the response contains no transparent pixels.
      Test wms:wmsops-getmap-params-transparent-2 Passed
      Testing wms:wmsops-getmap-params-transparent-3 (wms-1.1.1/d39e2617_1)...
         Assertion: When a GetMap request is made with TRANSPARENT=TRUE and a FORMAT that supports transparency over a BBOX that is not completely covered, then the response contains transparent pixels.
      Test wms:wmsops-getmap-params-transparent-3 Passed
      Testing wms:wmsops-getmap-params-version-1 (wms-1.1.1/d39e2631_1)...
         Assertion: When a GetMap request is made using WMTVER instead of VERSION, the response is valid.
      Test wms:wmsops-getmap-params-version-1 Passed
      Testing wms:wmsops-getmap-params-width_height-1 (wms-1.1.1/d39e2645_1)...
         Assertion: When a request is made with WIDTH=1024 and HEIGHT=768, the image returned is exactly the size requested.
      Test wms:wmsops-getmap-params-width_height-1 Passed
      Testing wms:wmsops-getmap-params-width_height-2 (wms-1.1.1/d39e2664_1)...
         Assertion: When a request is made with WIDTH=16 and HEIGHT=16, the image returned is exactly the size requested.
      Test wms:wmsops-getmap-params-width_height-2 Passed
      Testing wms:wmsops-getfeatureinfo-each-info_format (wms-1.1.1/d39e2680_1)...
         Assertion: For each advertised GetFeatureInfo format, when a GetFeatureInfo request is made with the INFO_FORMAT parameter set to the format, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-each-info_format Passed
      Testing wms:wmsops-getfeatureinfo-each-info_format (wms-1.1.1/d39e2680_2)...
         Assertion: For each advertised GetFeatureInfo format, when a GetFeatureInfo request is made with the INFO_FORMAT parameter set to the format, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-each-info_format Passed
      Testing wms:wmsops-getfeatureinfo-each-info_format (wms-1.1.1/d39e2680_3)...
         Assertion: For each advertised GetFeatureInfo format, when a GetFeatureInfo request is made with the INFO_FORMAT parameter set to the format, then the Content-type header returned is the same.
      Test wms:wmsops-getfeatureinfo-each-info_format Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_1)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_2)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_3)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_4)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_5)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_6)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_7)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_8)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_9)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_10)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-style (wms-1.1.1/d39e2691_11)...
         Assertion: For each of the Styles in the capabilities document, when a GetMap request is made with the STYLES parameter set to the element of the style, then the response is valid.
      Test wms:wmsops-getmap-each-style Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_1)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_2)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_3)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_4)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_5)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_6)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_7)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_8)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_9)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_10)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-layer (wms-1.1.1/d39e2701_11)...
         Assertion: For each of the Layers in the capabilities document, when a GetMap request is made with the LAYERS parameter set to the element of the layer, then the response is valid.
      Test wms:wmsops-getmap-each-layer Passed
      Testing wms:wmsops-getmap-each-srs (wms-1.1.1/d39e2711_1)...
         Assertion: For each SRS in the capabilities document, when a GetMap request uses the SRS, then the response is valid.
      Test wms:wmsops-getmap-each-srs Passed
      Testing wms:wmsops-getmap-layer-encoded-name (wms-1.1.1/d39e2739_1)...
         Assertion: When a layer is requested using encoded characters in its name, the response is a map.
      Test wms:wmsops-getmap-layer-encoded-name Passed
      Testing wms:basic_elements-validate-exception (wms-1.1.1/d39e2745_1)...
         Assertion: When an exception is generated, it validates.
      Test wms:basic_elements-validate-exception Passed
   Test wms:main Failed (Inherited failure)
Suite wms:main_wms Failed
<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools&gt;
cp target/sessions/session.xml.wms-1.1.1 users/geoserver/wms-1.1.1/session.xml
Test wms:main (wms-1.1.1) Failed (Inherited Failure)
   Test wms:wmsops-getcapabilities-response-2 (wms-1.1.1/d39e1639_1) Failed
RETURN=1
Pinging GeoServer at http://localhost:11010/geoserver

curl: (7) couldn't connect to host
GeoServer is offline

On Wed, 2011-01-05 at 10:29 -0700, Justin Deoliveira wrote:

Hmmm... what version of the tests are you running?

just followed the README in community/cite to the letter and ran the
test suite through run.sh wms-1.1.1.
The VendorSpecificCapabilities failure hudson is reported should be
fixed now, but it keeps complaining when I do a manual run in hudson.
How does the cite-wms-1.1.1 hudson build is run? does it depend of a
geoserver trunk build, nightly, or deploy?

I just looked at the sources of those tests and it looks like the
WMTVER rather than VERSION parameter should be used. But it does not
look like it with the url you posted in. Are you positive that is the
url being requested?

Didn't debug it, but that's the URL the test log says it's issuing?
Could this be to a badly applied patch (one of the ones in the README)?
cause I couldn't run the suite through jetty.

On Wed, Jan 5, 2011 at 9:42 AM, Gabriel Roldán <groldan@anonymised.com>
wrote:
        I fixed the cite failure I recognized as my fault (empty
        VendorSpecificCapabilities), but now when I run it locally it
        the
        following assertion fails:
        
        <quote>
        Test wms:wmsops-getcapabilities-params-request-1
        (wms-1.1.1/d40e1042_1)
        
        Assertion: When REQUEST is &quot;capabilities&quot;, then the
        response
        is capabilities XML.
        
        Request d40e3116_1:
          Method: get
          URL:
        http://localhost:9090/geoserver/wms?SERVICE=WMS&&SeRvIcE=WMS&ReQuEsT=capabilities
          Response from parser ::
             <WMS_Capabilities xmlns="http://www.opengis.net/wms&quot;
        </quote>
        
        Now, the capabilities URL I gave to the test engine has the
        version=1.1.1 parameter, not sure why the engine is trying the
        above
        request without version parameter, and hence the failure is
        due to the
        WMS 1.3 getcaps being returned instead of the 1.1.1 ones.
        
        Any clue?
        
        Cheers,
        Gabriel
        
        On Wed, 2011-01-05 at 06:47 +0000, Hudson wrote:
        > See
        <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/&gt;
        >
        > ------------------------------------------
        > [...truncated 1147 lines...]
        ...
        > Test wms:main Failed (Inherited failure)
        > Suite wms:main_wms Failed
        >
        <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools&gt;
        > cp target/sessions/session.xml.wms-1.1.1
        users/geoserver/wms-1.1.1/session.xml
        > Test wms:main (wms-1.1.1) Failed (Inherited Failure)
        > Test wms:wmsops-getcapabilities-response-2
        (wms-1.1.1/d39e1639_1) Failed
        > RETURN=1
        > Pinging GeoServer at http://localhost:11010/geoserver
        >
        > curl: (7) couldn't connect to host
        > GeoServer is offline
        >
        
        ------------------------------------------------------------------------------
        Learn how Oracle Real Application Clusters (RAC) One Node
        allows customers
        to consolidate database storage, standardize their database
        environment, and,
        should the need arise, upgrade to a full multi-node Oracle RAC
        database
        without downtime or disruption
        http://p.sf.net/sfu/oracle-sfdevnl
        _______________________________________________
        Geoserver-devel mailing list
        Geoserver-devel@lists.sourceforge.net
        https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

--
Gabriel Roldan
groldan@anonymised.com
Expert service straight from the developers

On Wed, Jan 5, 2011 at 5:42 PM, Gabriel Roldán <groldan@anonymised.com> wrote:

I fixed the cite failure I recognized as my fault (empty
VendorSpecificCapabilities), but now when I run it locally it the
following assertion fails:

<quote>
Test wms:wmsops-getcapabilities-params-request-1 (wms-1.1.1/d40e1042_1)

Assertion: When REQUEST is &quot;capabilities&quot;, then the response
is capabilities XML.

Request d40e3116_1:
Method: get
URL:
http://localhost:9090/geoserver/wms?SERVICE=WMS&&SeRvIcE=WMS&ReQuEsT=capabilities
Response from parser ::
<WMS_Capabilities xmlns="http://www.opengis.net/wms&quot;
</quote>

Now, the capabilities URL I gave to the test engine has the
version=1.1.1 parameter, not sure why the engine is trying the above
request without version parameter, and hence the failure is due to the
WMS 1.3 getcaps being returned instead of the 1.1.1 ones.

Any clue?

Sounds similar to a WCS cite test issue, one cannot run WCS 1.0 cite tests with
WCS 1.1 around for the same problem (I believe, it may be the other way around
but I'm not sure).

If this is it, it's basically lack of future proofing in the older
version of the tests, they
did not care about what would happen if a newer version of the same protocol
was around in the same server.

It would be indeed nice to be able to disable a specific version of a protocol
by config, instead of shutting down a service entirely like we have now

My 2 cents

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

Sadly those instructions are out of date. Sigh… the cite testing story right now is quite a mess.

What I will do is zip up the cite testing tools that i have on the build server and make those available for download, encouraging devs to just run the tests from that. With all the patches I have had to make it has become tricky to manage.

More shortly.

-Justin

On Wed, Jan 5, 2011 at 10:42 AM, Gabriel Roldán <groldan@anonymised.com> wrote:

On Wed, 2011-01-05 at 10:29 -0700, Justin Deoliveira wrote:

Hmmm… what version of the tests are you running?

just followed the README in community/cite to the letter and ran the
test suite through run.sh wms-1.1.1.
The VendorSpecificCapabilities failure hudson is reported should be
fixed now, but it keeps complaining when I do a manual run in hudson.
How does the cite-wms-1.1.1 hudson build is run? does it depend of a
geoserver trunk build, nightly, or deploy?

I just looked at the sources of those tests and it looks like the
WMTVER rather than VERSION parameter should be used. But it does not
look like it with the url you posted in. Are you positive that is the
url being requested?

Didn’t debug it, but that’s the URL the test log says it’s issuing?
Could this be to a badly applied patch (one of the ones in the README)?
cause I couldn’t run the suite through jetty.

On Wed, Jan 5, 2011 at 9:42 AM, Gabriel Roldán <groldan@anonymised.com>
wrote:
I fixed the cite failure I recognized as my fault (empty
VendorSpecificCapabilities), but now when I run it locally it
the
following assertion fails:

Test wms:wmsops-getcapabilities-params-request-1 (wms-1.1.1/d40e1042_1)

Assertion: When REQUEST is "capabilities", then the
response
is capabilities XML.

Request d40e3116_1:
Method: get
URL:
http://localhost:9090/geoserver/wms?SERVICE=WMS&&SeRvIcE=WMS&ReQuEsT=capabilities
Response from parser ::
<WMS_Capabilities xmlns=“http://www.opengis.net/wms

Now, the capabilities URL I gave to the test engine has the
version=1.1.1 parameter, not sure why the engine is trying the
above
request without version parameter, and hence the failure is
due to the
WMS 1.3 getcaps being returned instead of the 1.1.1 ones.

Any clue?

Cheers,
Gabriel

On Wed, 2011-01-05 at 06:47 +0000, Hudson wrote:

See
<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/>


[…truncated 1147 lines…]

Test wms:main Failed (Inherited failure)
Suite wms:main_wms Failed

<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools>

cp target/sessions/session.xml.wms-1.1.1
users/geoserver/wms-1.1.1/session.xml
Test wms:main (wms-1.1.1) Failed (Inherited Failure)
Test wms:wmsops-getcapabilities-response-2
(wms-1.1.1/d39e1639_1) Failed
RETURN=1
Pinging GeoServer at http://localhost:11010/geoserver

curl: (7) couldn’t connect to host
GeoServer is offline


Learn how Oracle Real Application Clusters (RAC) One Node
allows customers
to consolidate database storage, standardize their database
environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC
database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl


Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.


Gabriel Roldan
groldan@anonymised.com
Expert service straight from the developers


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Ok, i have packed up the cite tools and updated the cite README. This packed up version contains all the hacks that I had to put in place to get the tests to run. Feel free to examine the svn diffs.

http://files.opengeo.org/cite_tools.tgz

Once someone else (Andrea or Gabriel) tries this out and verifies it actually works I will update the online release guide documentation.

I will also probably create a github repo or something to store all of this so that (a) if the build server goes bye bye we won’t lose the patches and (b) we can still leave it linked to ogc svn.

-Justin

On Wed, Jan 5, 2011 at 10:48 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Sadly those instructions are out of date. Sigh… the cite testing story right now is quite a mess.

What I will do is zip up the cite testing tools that i have on the build server and make those available for download, encouraging devs to just run the tests from that. With all the patches I have had to make it has become tricky to manage.

More shortly.

-Justin

On Wed, Jan 5, 2011 at 10:42 AM, Gabriel Roldán <groldan@anonymised.com> wrote:

On Wed, 2011-01-05 at 10:29 -0700, Justin Deoliveira wrote:

Hmmm… what version of the tests are you running?

just followed the README in community/cite to the letter and ran the
test suite through run.sh wms-1.1.1.
The VendorSpecificCapabilities failure hudson is reported should be
fixed now, but it keeps complaining when I do a manual run in hudson.
How does the cite-wms-1.1.1 hudson build is run? does it depend of a
geoserver trunk build, nightly, or deploy?

I just looked at the sources of those tests and it looks like the
WMTVER rather than VERSION parameter should be used. But it does not
look like it with the url you posted in. Are you positive that is the
url being requested?

Didn’t debug it, but that’s the URL the test log says it’s issuing?
Could this be to a badly applied patch (one of the ones in the README)?
cause I couldn’t run the suite through jetty.

On Wed, Jan 5, 2011 at 9:42 AM, Gabriel Roldán <groldan@anonymised.com>
wrote:
I fixed the cite failure I recognized as my fault (empty
VendorSpecificCapabilities), but now when I run it locally it
the
following assertion fails:

Test wms:wmsops-getcapabilities-params-request-1 (wms-1.1.1/d40e1042_1)

Assertion: When REQUEST is "capabilities", then the
response
is capabilities XML.

Request d40e3116_1:
Method: get
URL:
http://localhost:9090/geoserver/wms?SERVICE=WMS&&SeRvIcE=WMS&ReQuEsT=capabilities
Response from parser ::
<WMS_Capabilities xmlns=“http://www.opengis.net/wms

Now, the capabilities URL I gave to the test engine has the
version=1.1.1 parameter, not sure why the engine is trying the
above
request without version parameter, and hence the failure is
due to the
WMS 1.3 getcaps being returned instead of the 1.1.1 ones.

Any clue?

Cheers,
Gabriel

On Wed, 2011-01-05 at 06:47 +0000, Hudson wrote:

See
<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/>


[…truncated 1147 lines…]

Test wms:main Failed (Inherited failure)
Suite wms:main_wms Failed

<http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools>

cp target/sessions/session.xml.wms-1.1.1
users/geoserver/wms-1.1.1/session.xml
Test wms:main (wms-1.1.1) Failed (Inherited Failure)
Test wms:wmsops-getcapabilities-response-2
(wms-1.1.1/d39e1639_1) Failed
RETURN=1
Pinging GeoServer at http://localhost:11010/geoserver

curl: (7) couldn’t connect to host
GeoServer is offline


Learn how Oracle Real Application Clusters (RAC) One Node
allows customers
to consolidate database storage, standardize their database
environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC
database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl


Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.


Gabriel Roldan
groldan@anonymised.com
Expert service straight from the developers


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.