Hi,
today I built the teamengine war, deployed in tomcat along with the necessary dependencies, and started it to make a wfs 1.0.0 test against
trunk. Now, the moment I chose the wfs 1.0.0 test Tomcat started
cheewing cpu... I said myself, ok, the engine is chewing the xml,
I'll have to wait a few minutes. Well, after 30 minutes wait I killed
it...
Then I tried to run the wfs 1.0.0 tests from the command line using
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite>engine\bin\test -logdir=target/logs -source=tests\wfs\1.0.0\ets\ctl\wfs.xml -session=wfs-1.0.0
29-gen-2008 10.34.51 com.occamlab.te.Test <init>
INFO: Initializing main test driver
29-gen-2008 10.34.53 com.occamlab.te.Test <init>
INFO: Processing source(s) at: C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\engine\apps\engine\resources\com\occamlab\te\scripts
29-gen-2008 10.34.53 com.occamlab.te.Test <init>
INFO: Processing source(s) at: C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\tests\wfs\1.0.0\ets\ctl\wfs.xml
Testing wfs:main (wfs-1.0.0)...
Assertion: This WFS is valid
(and then the Swing UI popped up)
and that took some 5 minutes. So my wild guess it that the war
chews all of the tests suites xml before running so I run out of patience too early? Seriously, how they think that the teamengine first run is ok taking 30+ minutes??? Or is it me doing something wrong?
Oh, I also tried to run the wfs 1.1.0 tests alone by using the following
command line (using the custom run.bat that should ease up the interactive usage):
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite>run wfs 1.1.0 wfs-1.1.0
29-gen-2008 10.29.49 com.occamlab.te.Test <init>
INFO: Initializing main test driver
29-gen-2008 10.29.50 com.occamlab.te.Test <init>
INFO: Processing source(s) at: C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\engine\apps\engine\resources\com\occamlab\te\scripts
29-gen-2008 10.29.50 com.occamlab.te.Test <init>
INFO: Processing source(s) at: C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\tests\wfs\1.1.0\ets\ctl\main.xml
Exception in thread "CTL Test Engine" java.lang.NullPointerException
at com.occamlab.te.Test.getTemplateFromLog(Test.java:379)
at com.occamlab.te.Test.test(Test.java:448)
at com.occamlab.te.Test.main(Test.java:677)
Hmm... what's wrong here?
Cheers
Andrea
Andrea Aime wrote:
Hi,
today I built the teamengine war, deployed in tomcat along with the
necessary dependencies, and started it to make a wfs 1.0.0 test against
trunk. Now, the moment I chose the wfs 1.0.0 test Tomcat started
cheewing cpu... I said myself, ok, the engine is chewing the xml,
I'll have to wait a few minutes. Well, after 30 minutes wait I killed
it...
I have never really tried to run with tomcat. I usually run command
line. And I know... its slow. Dont worry, I have complained about this
many times. I will bring it up in this weeks meeting again 
All the time is spent building the "internal" stylesheet from all the
test scripts? Are you loading all the scripts? Perhaps only loading the
scripts for the suite you want to run would make it faster. Actually
this might be something we can apply to running from the command line
since one of the tasks is copying all teh test sources into the script
directory. I will look into this.
Then I tried to run the wfs 1.0.0 tests from the command line using
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite>engine\bin\test
-logdir=target/logs -source=tests\wfs\1.0.0\ets\ctl\wfs.xml
-session=wfs-1.0.0
29-gen-2008 10.34.51 com.occamlab.te.Test <init>
INFO: Initializing main test driver
29-gen-2008 10.34.53 com.occamlab.te.Test <init>
INFO: Processing source(s) at:
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\engine\apps\engine\resources\com\occamlab\te\scripts
29-gen-2008 10.34.53 com.occamlab.te.Test <init>
INFO: Processing source(s) at:
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\tests\wfs\1.0.0\ets\ctl\wfs.xml
Testing wfs:main (wfs-1.0.0)...
Assertion: This WFS is valid
(and then the Swing UI popped up)
and that took some 5 minutes. So my wild guess it that the war
chews all of the tests suites xml before running so I run out of
patience too early? Seriously, how they think that the teamengine first
run is ok taking 30+ minutes??? Or is it me doing something wrong?
Again.. i feel your pain. 5 minutes does seem a bit high though...
Usually it takes 2-3 on my pc... which afaik is much slower than yours :).
Oh, I also tried to run the wfs 1.1.0 tests alone by using the following
command line (using the custom run.bat that should ease up the
interactive usage):
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite>run wfs
1.1.0 wfs-1.1.0
29-gen-2008 10.29.49 com.occamlab.te.Test <init>
INFO: Initializing main test driver
29-gen-2008 10.29.50 com.occamlab.te.Test <init>
INFO: Processing source(s) at:
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\engine\apps\engine\resources\com\occamlab\te\scripts
29-gen-2008 10.29.50 com.occamlab.te.Test <init>
INFO: Processing source(s) at:
C:\progetti\geoserver\src\trunkClean\geoserver\community\cite\tests\wfs\1.1.0\ets\ctl\main.xml
Exception in thread "CTL Test Engine" java.lang.NullPointerException
at com.occamlab.te.Test.getTemplateFromLog(Test.java:379)
at com.occamlab.te.Test.test(Test.java:448)
at com.occamlab.te.Test.main(Test.java:677)
Hmm... what's wrong here?
I think it might be a stale test suite. Try removing the
target/logs/wfs-1.0.0 directory and try again
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,479ef579256341137850744!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org