[Geoserver-devel] How can hudson show successfull geoserver builds ???

Hi all

I am pretty confused about our offical hudson build server which shows perfect builds for geoserver-trunk and geoserver-2.0.x
Since some time, I never succeeded with with a geoserver build using SUN sdk or IBM SDK or OpenJDK.

Investigating further into FeatureChainingWfsTest>>testDescribeFeatureType if found the problem at line 160

assertXpathEvaluatesTo(AbstractAppSchemaMockData.GSML_URI, "//xsd:import[1]/@namespace",doc)

which tries to query the "namespace" attribute of the second "import" Element. According to W3C, indexing starts with 1 and not with 0, it has to be

assertXpathEvaluatesTo(AbstractAppSchemaMockData.GSML_URI, "//xsd:import[2]/@namespace",doc)

After fixing and a retry, line 188 causes the next problem.

@Ben, could you have a look at this. I do not want to open an issue because of the successfull hudson builds.

Christian,

this is a build failure on your platform and so a Jira issue is entirely appropriate. I have created one for your convenience:
http://jira.codehaus.org/browse/GEOS-3689

Please add yourself as a watcher.

A cursory examination suggests that this is a problem we have often seen before, in various guises: the unwarranted assumption that HashMap iteration order is the same across platforms.

HashMap explicitly makes no guarantees whatsoever about iteration order. It is not guaranteed that order is preserved over time or across platforms. The GeoServer Catalog makes extensive use of HashMap in its implementation. Either the catalog or the app-schema implementation is using a HashMap, and the unit tests are assuming a fixed iteration order.

I will see if I can fix this.

Kind regards,
Ben.

On 01/12/09 22:26, Christian Müller wrote:

Hi all

I am pretty confused about our offical hudson build server which shows
perfect builds for geoserver-trunk and geoserver-2.0.x
Since some time, I never succeeded with with a geoserver build using SUN sdk
or IBM SDK or OpenJDK.

Investigating further into FeatureChainingWfsTest>>testDescribeFeatureType
if found the problem at line 160

  assertXpathEvaluatesTo(AbstractAppSchemaMockData.GSML_URI,
"//xsd:import[1]/@namespace",doc)

which tries to query the "namespace" attribute of the second "import"
Element. According to W3C, indexing starts with 1 and not with 0, it has to
be

  assertXpathEvaluatesTo(AbstractAppSchemaMockData.GSML_URI,
"//xsd:import[2]/@namespace",doc)

After fixing and a retry, line 188 causes the next problem.

@Ben, could you have a look at this. I do not want to open an issue because
of the successfull hudson builds.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia