[Geoserver-devel] Running CITE tests from the command line

Tom,

for this week's release I will use the latest te-2015 CITE teamengine (FOSS4G sprint plus Andrea with fixes from Brad). If GeoServer does not start in Jetty I will test against Tomcat. I will report back on any Jetty failures.

Kind regards,
Ben.

On 18/11/15 02:32, Tom Ingold wrote:

Ben,

The working directory for the cite tests is the /var/lib/jenkins/workspace/geoserver-cite directory and the tests that are failing all get run by invoking “run.sh wcs-1.0 2.8.x” to run the WCS 1.0 tests on the 2.8 branch…change to wcs-1.1 to run WCS 1.10 tests (you get the idea).

That script unzips a fresh version of the geoserver bin into a working directory and attempts to start it pointing at a special data_dir with dat for the cite tests. There was an error with the new jetty not honoring the testing port (11010) and conflicting with Jenkins on 8080 but I fixed that (those scripts are a mess and need some love).

The problem now is that the GeoTools logger blows up when Jetty starts, so GeoServer deploy fails and — while Jetty is technically up and answering requests -- all the tests fail as the get 404s when making requests. Not sure why GeoTools is failing, I try to run the geoserver-bin in other places and it works fine - so there is something fishy about how this particular environment is being setup.

On travel right now and don’t have all that much time to work it —but will do what I can….anyone else have ideas?

Cheers,

Tom

:25.180::WARN: failed HandlerCollection@anonymised.com
java.lang.NoClassDefFoundError: Could not initialize class org.apache.log4j.Logger
  at org.geotools.util.logging.Log4JLoggerFactory.getImplementation(Log4JLoggerFactory.java:65)
  at org.geotools.util.logging.Log4JLoggerFactory.getImplementation(Log4JLoggerFactory.java:33)
  at org.geotools.util.logging.LoggerFactory.getLogger(LoggerFactory.java:79)
  at org.geotools.util.logging.Logging.getLogger(Logging.java:200)
  at org.geoserver.platform.GeoServerResourceLoader.<clinit>(GeoServerResourceLoader.java:62)
  at org.geoserver.logging.LoggingStartupContextListener.contextInitialized(LoggingStartupContextListener.java:66)
  at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:540)
  at org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
  at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1220)
  at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:510)
  at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448)
  at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
  at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
  at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
  at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
  at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
  at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
  at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
  at org.mortbay.jetty.Server.doStart(Server.java:222)
  at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
  at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:606)
  at org.mortbay.start.Main.invokeMain(Main.java:183)
  at org.mortbay.start.Main.start(Main.java:497)
  at org.mortbay.start.Main.main(Main.java:115)

Tom Ingold

VP, Product
Boundless
Desk: 202.827.0299
Mobile: 813.784.4151

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

On Tue, Nov 17, 2015 at 7:47 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Tom,

for this week's release I will use the latest te-2015 CITE teamengine
(FOSS4G sprint plus Andrea with fixes from Brad). If GeoServer does not
start in Jetty I will test against Tomcat. I will report back on any Jetty
failures.

Is that the latest? You will get a boatload of failures with that, we are
not up to date, OGC changed the what it means to
be compliant on our back. I've been trying to get an upgrade of the CITE
tests for months now but... well, it seems there
is no time to dedicate to it build server wise

Cheers
Andrea

--

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.

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

On 18/11/15 07:50, Andrea Aime wrote:

On Tue, Nov 17, 2015 at 7:47 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

for this week's release I will use the latest te-2015 CITE teamengine
(FOSS4G sprint plus Andrea with fixes from Brad). If GeoServer does not
start in Jetty I will test against Tomcat. I will report back on any Jetty
failures.

Is that the latest? You will get a boatload of failures with that, we are
not up to date, OGC changed the what it means to
be compliant on our back. I've been trying to get an upgrade of the CITE
tests for months now but... well, it seems there
is no time to dedicate to it build server wise

I think between you and Brad and Torben and changing some of the CITE submodules there is much that works (and I want to see for myself):
http://osgeo-org.1560.x6.nabble.com/New-CITE-test-tooling-ready-for-the-brave-td5218120.html

I intend to get some long term benefit for the project from my manual CITE testing. I am reluctant to use the old test suite when it cannot even be compiled using the documented instructions. The new te-2015 branch at least compiles.

In today's meeting I want to discuss what it means for a release to be CITE compliant.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand