Thanks, Andrea. This is a genuine failure. The ex targetNamespace code branch of this test was not updated for GEOS-7860, which adds an additional schema. Please try this fix locally (as I do not see this failure) and then merge if it works: https://github.com/geoserver/geoserver/pull/2014
See also: https://osgeo-org.atlassian.net/browse/GEOS-7860 Kind regards, Ben. On 12/12/16 20:42, Andrea Aime wrote: > Hi Ben, > I get the following: > > Error while parsing JAI registry file > "file:/home/aaime/.m2/repository/org/geotools/gt-coverage/16-SNAPSHOT/gt-coverage-16-SNAPSHOT.jar!/META-INF/registryFile.jai" > : > Error in registry file at line number #31 > A descriptor is already registered against the name > "org.geotools.ColorReduction" under registry mode "rendered" > Error in registry file at line number #32 > A descriptor is already registered against the name > "org.geotools.ColorInversion" under registry mode "rendered" > Error while parsing JAI registry file > "file:/home/aaime/.m2/repository/org/geotools/gt-process-raster/16-SNAPSHOT/gt-process-raster-16-SNAPSHOT.jar!/META-INF/registryFile.jai" > : > Error in registry file at line number #4 > A descriptor is already registered against the name "ClassBreaks" under > registry mode "rendered" > dic 12, 2016 8:42:07 AM org.geoserver.test.FeatureChainingWfsTest > testDescribeFeatureTypeNoTypes > INFORMAZIONI: WFS DescribeFeatureType response: > <?xml version="1.0" encoding="UTF-8"?> > <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > elementFormDefault="qualified" targetNamespace="http://example.com";> > <xsd:include > schemaLocation="file:/home/aaime/devel/git-gs/src/extension/app-schema/app-schema-test/target/app-schema-mock819895118180371408data/featureTypes/ex_SecondParentFeature/simpleContent.xsd"/> > <xsd:include > schemaLocation="file:/home/aaime/devel/git-gs/src/extension/app-schema/app-schema-test/target/app-schema-mock819895118180371408data/featureTypes/ex_ParentFeature/NonValidNestedGML.xsd"/> > <xsd:include > schemaLocation="file:/home/aaime/devel/git-gs/src/extension/app-schema/app-schema-test/target/app-schema-mock819895118180371408data/featureTypes/ex_FirstParentFeature/simpleContent.xsd"/> > <xsd:import namespace="urn:cgi:xmlns:CGI:GeoSciML:2.0" schemaLocation=" > http://www.geosciml.org/geosciml/2.0/xsd/geosciml.xsd"/> > <xsd:import namespace="http://www.opengis.net/om/1.0"; schemaLocation=" > http://schemas.opengis.net/om/1.0.0/observation.xsd"/> > </xsd:schema> > > Cheers > Andrea > > On Mon, Dec 12, 2016 at 4:50 AM, Ben Caradoc-Davies <[email protected]> > wrote: > >> Andrea, >> >> this tests passes for me in Maven and Eclipse on OpenJDK 8. >> >> A comment in the test warns: >> // targetNamespace depends on load order which is platform dependent >> >> What do you see at the console if you run this test in Eclipse? The >> failure you see indicates that you are getting the example (ex) >> targetNamespace. I would like to see your response document so I can >> determine if it is valid. >> >> I get the GeoSciML targetNamespace which passes the test (second branch): >> >> Dec 12, 2016 4:33:36 PM org.geoserver.test.FeatureChainingWfsTest >> testDescribeFeatureTypeNoTypes >> INFO: WFS DescribeFeatureType response: >> <?xml version="1.0" encoding="UTF-8"?> >> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >> elementFormDefault="qualified" targetNamespace="urn:cgi:xmlns >> :CGI:GeoSciML:2.0"> >> <xsd:import namespace="http://example.com"; >> schemaLocation="file:/home/ben/geoserver/src%20with%20spaces >> /geoserver/src/extension/app-schema/app-schema-test/target/ >> app-schema-mock578553865686759165data/featureTypes/ex_ >> ParentFeature/NonValidNestedGML.xsd"/> >> <xsd:include schemaLocation="http://www.geo >> sciml.org/geosciml/2.0/xsd/geosciml.xsd"/> >> <xsd:import namespace="http://www.opengis.net/om/1.0"; schemaLocation=" >> http://schemas.opengis.net/om/1.0.0/observation.xsd"/> >> </xsd:schema> >> >> Kind regards, >> Ben. >> >> >> >> On 12/12/16 08:24, Andrea Aime wrote: >> >>> Hi, >>> I do have a test that keeps on failing locally on my machine: >>> >>> Tests run: 27, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 12.52 sec >>> <<< FAILURE! >>> testDescribeFeatureTypeNoTypes(org.geoserver.test.FeatureChainingWfsTest) >>> Time elapsed: 15 sec <<< FAILURE! >>> java.lang.AssertionError: expected:<2> but was:<3> >>> at org.junit.Assert.fail(Assert.java:88) >>> at org.junit.Assert.failNotEquals(Assert.java:743) >>> at org.junit.Assert.assertEquals(Assert.java:118) >>> at org.junit.Assert.assertEquals(Assert.java:555) >>> at org.junit.Assert.assertEquals(Assert.java:542) >>> at >>> org.geoserver.test.FeatureChainingWfsTest.testDescribeFeatureTypeNoTypes( >>> FeatureChainingWfsTest.java:325) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce >>> ssorImpl.java:62) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>> thodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:498) >>> at >>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall( >>> FrameworkMethod.java:47) >>> at >>> org.junit.internal.runners.model.ReflectiveCallable.run(Refl >>> ectiveCallable.java:12) >>> at >>> org.junit.runners.model.FrameworkMethod.invokeExplosively(Fr >>> ameworkMethod.java:44) >>> at >>> org.junit.internal.runners.statements.InvokeMethod.evaluate( >>> InvokeMethod.java:17) >>> at >>> org.junit.internal.runners.statements.RunBefores.evaluate( >>> RunBefores.java:26) >>> at >>> org.junit.internal.runners.statements.RunAfters.evaluate(Run >>> Afters.java:27) >>> at org.junit.rules.RunRules.evaluate(RunRules.java:20) >>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) >>> at >>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit >>> 4ClassRunner.java:70) >>> at >>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit >>> 4ClassRunner.java:50) >>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) >>> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) >>> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) >>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) >>> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) >>> at >>> org.junit.internal.runners.statements.RunBefores.evaluate( >>> RunBefores.java:26) >>> at >>> org.junit.internal.runners.statements.RunAfters.evaluate(Run >>> Afters.java:27) >>> at org.junit.runners.ParentRunner.run(ParentRunner.java:309) >>> at >>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUni >>> t4Provider.java:252) >>> at >>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestS >>> et(JUnit4Provider.java:141) >>> at >>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit >>> 4Provider.java:112) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce >>> ssorImpl.java:62) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>> thodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:498) >>> at >>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodW >>> ithArray(ReflectionUtils.java:189) >>> at >>> org.apache.maven.surefire.booter.ProviderFactory$ProviderPro >>> xy.invoke(ProviderFactory.java:165) >>> at >>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvi >>> der(ProviderFactory.java:85) >>> at >>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPro >>> cess(ForkedBooter.java:115) >>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBoo >>> ter.java:75) >>> >>> At first I thought "hey, my geotools checkout is not up to date", and >>> indeed I was missing some commits, >>> then I've tried getting jars from the boundless repo instead, but the >>> outcome does not change. >>> I've run the test in Eclipse, and fails the same way. >>> >>> Checking the windows and openjdk build servers, they also failing the same >>> way: >>> http://winbuild.geo-solutions.it/jenkins/job/GeoServer-Maste >>> r/lastCompletedBuild/testReport/ >>> http://build.geo-solutions.it/jenkins/job/GeoServer-Master-O >>> penJDK8/1185/consoleFull >>> >>> Anyone has a clue as to what might be causing this? >>> >>> Cheers >>> Andrea >>> >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Developer Access Program for Intel Xeon Phi Processors >>> Access to Intel Xeon Phi processor-based developer platforms. >>> With one year of Intel Parallel Studio XE. >>> Training and support from Colfax. >>> Order your platform today.http://sdm.link/xeonphi >>> >>> >>> >>> _______________________________________________ >>> Geoserver-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >>> >> -- >> Ben Caradoc-Davies <[email protected]> >> Director >> Transient Software Limited <http://transient.nz/> >> New Zealand >> > > > -- 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
