[Geoserver-devel] Strange unti test failures when running localy

I've been getting some strange unit test failures that only seem to
occur on my machine.

Some in the WFS module that appear and disappear depending on how the
tests are run.

org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithMatchingUrnBboxFilter()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithSRS()
org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBboxFilter()
org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBoundsEnabled()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithSillyLiteral()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithGmlObjectId()

If I run all the GeoServer unit tests, they fail, but if I just run the
WFS Module by itself, or resume from :gs-wfs they pass. In Eclipse,
running the WFS module's tests together fails, but running the tests
individually passes. They all seem to be caused by service exceptions.

The other test is failing consistently:

org.geoserver.wps.ogr.WPSOgrTest.testOGRKMLOutputExecuteDocument()

It's checking that there's a node in the XML matching
"//kml:kml/kml:Document/kml:Schema", but the the Schema node is inside a
Folder node inside the Document node rather than a direct child. I
don't know if this is a mistake in the test or if that extra element is
an error. If the folder is acceptable it's easy enough to correct the
XPath to "//kml:kml/kml:Document/kml:Schema |
//kml:kml/kml:Document/kml:Folder/kml:Schema" which will work either
way.

The WFS failures have been plaguing me on and off for over a month. The
OGR-WPS failure is new.

--
  Kevin Michael Smith
  smithkm@anonymised.com

Is it worth comparing maven / java versions? Anything unusual about your setup?

You may want to check the history of wfs and related modules “about a month” ago …

Since your tests seem to be around bbox and literals they maybe caused by changes to filter/expression handling?

In both cases I see optimization and date/time related work - but nothing specifically about bounding box :frowning:

Anyone else have ideas?

···

On 5 October 2015 at 19:13, Kevin Smith <smithkm@anonymised.com> wrote:

I’ve been getting some strange unit test failures that only seem to
occur on my machine.

Some in the WFS module that appear and disappear depending on how the
tests are run.

org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithMatchingUrnBboxFilter()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithSRS()
org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBboxFilter()
org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBoundsEnabled()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithSillyLiteral()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithGmlObjectId()

If I run all the GeoServer unit tests, they fail, but if I just run the
WFS Module by itself, or resume from :gs-wfs they pass. In Eclipse,
running the WFS module’s tests together fails, but running the tests
individually passes. They all seem to be caused by service exceptions.

The other test is failing consistently:

org.geoserver.wps.ogr.WPSOgrTest.testOGRKMLOutputExecuteDocument()

It’s checking that there’s a node in the XML matching
“//kml:kml/kml:Document/kml:Schema”, but the the Schema node is inside a
Folder node inside the Document node rather than a direct child. I
don’t know if this is a mistake in the test or if that extra element is
an error. If the folder is acceptable it’s easy enough to correct the
XPath to “//kml:kml/kml:Document/kml:Schema |
//kml:kml/kml:Document/kml:Folder/kml:Schema” which will work either
way.

The WFS failures have been plaguing me on and off for over a month. The
OGR-WPS failure is new.


Kevin Michael Smith
smithkm@anonymised.com



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


Jody Garnett

Hi Kevin,
you might want to modify those tests and set a higher logging level, in order to get
more information?

If that only happens during a long build it could also have to do with permgen or heap
settings, I know I recently had to kick the testing heap up to 512MB in order to make
the build work on ares.

Cheers
Andrea

···

On Tue, Oct 6, 2015 at 4:13 AM, Kevin Smith <smithkm@anonymised.com> wrote:

I’ve been getting some strange unit test failures that only seem to
occur on my machine.

Some in the WFS module that appear and disappear depending on how the
tests are run.

org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithMatchingUrnBboxFilter()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithSRS()
org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBboxFilter()
org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBoundsEnabled()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithSillyLiteral()
org.geoserver.wfs.v1_1.GetFeatureTest.testWithGmlObjectId()

If I run all the GeoServer unit tests, they fail, but if I just run the
WFS Module by itself, or resume from :gs-wfs they pass. In Eclipse,
running the WFS module’s tests together fails, but running the tests
individually passes. They all seem to be caused by service exceptions.

The other test is failing consistently:

org.geoserver.wps.ogr.WPSOgrTest.testOGRKMLOutputExecuteDocument()

It’s checking that there’s a node in the XML matching
“//kml:kml/kml:Document/kml:Schema”, but the the Schema node is inside a
Folder node inside the Document node rather than a direct child. I
don’t know if this is a mistake in the test or if that extra element is
an error. If the folder is acceptable it’s easy enough to correct the
XPath to “//kml:kml/kml:Document/kml:Schema |
//kml:kml/kml:Document/kml:Folder/kml:Schema” which will work either
way.

The WFS failures have been plaguing me on and off for over a month. The
OGR-WPS failure is new.


Kevin Michael Smith
smithkm@anonymised.com



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

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


Yes I’ve tried upping the memory to Maven and Surefire with no change and tweaking the tests is how I figured out that the extra Folder element was the problem.

The WFS error is related to the entity resolution security fix.

org.xml.sax.SAXException: Entity resolution disallowed for file:/home/smithkm/og-proj/geoserver/src/ows/target/classes/org/geoserver/ows/xml/v1_0/owsAll.xsd

Kevin Michael Smith

smithkm@anonymised.com

On Mon, Oct 5, 2015, at 11:18 PM, Andrea Aime wrote:

Hi Kevin,

you might want to modify those tests and set a higher logging level, in order to get

more information?

If that only happens during a long build it could also have to do with permgen or heap

settings, I know I recently had to kick the testing heap up to 512MB in order to make

the build work on ares.

Cheers

Andrea

On Tue, Oct 6, 2015 at 4:13 AM, Kevin Smith <smithkm@anonymised.com> wrote:

I’ve been getting some strange unit test failures that only seem to

occur on my machine.

Some in the WFS module that appear and disappear depending on how the

tests are run.

org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithMatchingUrnBboxFilter()

org.geoserver.wfs.v1_1.GetFeatureTest.testWithSRS()

org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBboxFilter()

org.geoserver.wfs.v1_1.GetFeatureTest.testPostWithBoundsEnabled()

org.geoserver.wfs.v1_1.GetFeatureTest.testWithSillyLiteral()

org.geoserver.wfs.v1_1.GetFeatureTest.testWithGmlObjectId()

If I run all the GeoServer unit tests, they fail, but if I just run the

WFS Module by itself, or resume from :gs-wfs they pass. In Eclipse,

running the WFS module’s tests together fails, but running the tests

individually passes. They all seem to be caused by service exceptions.

The other test is failing consistently:

org.geoserver.wps.ogr.WPSOgrTest.testOGRKMLOutputExecuteDocument()

It’s checking that there’s a node in the XML matching

“//kml:kml/kml:Document/kml:Schema”, but the the Schema node is inside a

Folder node inside the Document node rather than a direct child. I

don’t know if this is a mistake in the test or if that extra element is

an error. If the folder is acceptable it’s easy enough to correct the

XPath to "//kml:kml/kml:Document/kml:Schema |

//kml:kml/kml:Document/kml:Folder/kml:Schema" which will work either

way.

The WFS failures have been plaguing me on and off for over a month. The

OGR-WPS failure is new.


Kevin Michael Smith
smithkm@anonymised.com



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

==

GeoServer Professional Services from the experts! Visit

http://goo.gl/it488V for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.