You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@nagoya.apache.org> on 2004/11/26 10:34:20 UTC

Cocoon-2.1.X Tests Failure 11/26/04

Automated Cocoon Unit tests failed!

Full log file if this unit test run is available here:
http://nagoya.apache.org/~vadim/cocoon-test-log-20041126.log

Last messages from the log file:
==================================================================
  [foreach] reader-mime-type.xml:39: Starting http://localhost:18888///samples/test/reader-mime-type/test20.html
  [foreach] reader-mime-type.xml:41: Running test [Header: Content-type = text/html	... done (1ms)
  [foreach] reader-mime-type.xml:39: Finished http://localhost:18888///samples/test/reader-mime-type/test20.html (111ms)
  [foreach] reader-mime-type.xml:44: Starting http://localhost:18888///samples/test/reader-mime-type/test20.html
  [foreach] reader-mime-type.xml:46: Running test [Header: Content-type = text/html	... done (1ms)
  [foreach] reader-mime-type.xml:44: Finished http://localhost:18888///samples/test/reader-mime-type/test20.html (34ms)
  [foreach] reader-mime-type.xml:50: Starting http://localhost:18888///samples/test/reader-mime-type/test30.html
  [foreach] reader-mime-type.xml:52: Running test [Header: Content-type = text/html	... done (0ms)
  [foreach] reader-mime-type.xml:50: Finished http://localhost:18888///samples/test/reader-mime-type/test30.html (414ms)
  [foreach] reader-mime-type.xml:55: Starting http://localhost:18888///samples/test/reader-mime-type/test30.html
  [foreach] reader-mime-type.xml:57: Running test [Header: Content-type = text/html	... done (0ms)
  [foreach] reader-mime-type.xml:55: Finished http://localhost:18888///samples/test/reader-mime-type/test30.html (77ms)
  [foreach] reader-mime-type.xml:61: Starting http://localhost:18888///samples/test/reader-mime-type/test40.html
  [foreach] reader-mime-type.xml:63: Running test [Header: Content-type = text/html	... done (0ms)
  [foreach] reader-mime-type.xml:61: Finished http://localhost:18888///samples/test/reader-mime-type/test40.html (29ms)
  [foreach] reader-mime-type.xml:66: Starting http://localhost:18888///samples/test/reader-mime-type/test40.html
  [foreach] reader-mime-type.xml:68: Running test [Header: Content-type = text/html	... done (0ms)
  [foreach] reader-mime-type.xml:66: Finished http://localhost:18888///samples/test/reader-mime-type/test40.html (26ms)
  [foreach] reader-mime-type.xml:72: Starting http://localhost:18888///samples/test/reader-mime-type/test50.html
  [foreach] reader-mime-type.xml:74: Running test [Header: Content-type = text/html[1;31m		Failure: file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/cocoon-2.1.7-dev/test/anteater/reader-mime-type.xml:74:  message doesn't match because header 'content-type' is not present[m
  [foreach] 	... done (7ms)
  [foreach] reader-mime-type.xml:72: Finished http://localhost:18888///samples/test/reader-mime-type/test50.html (43ms)
BUILD FAILED
file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/cocoon-2.1.7-dev/test/anteater/reader-mime-type.xml:72: Task at file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/cocoon-2.1.7-dev/test/anteater/reader-mime-type.xml:72:  failed
Total time: 24 seconds

Last messages from the server console:
==================================================================
[Server@18b3e62]: Startup sequence initiated from main() method
[Server@18b3e62]: Loaded properties from [/disk/raid0/home/vadim/svn/cocoon-2.1.X/server.properties]
[Server@18b3e62]: Initiating startup sequence...
[Server@18b3e62]: Server socket opened successfully in 7 ms.
[Server@18b3e62]: Database [index=0, id=0, db=file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/webapp/WEB-INF/db/cocoondb, alias=] opened sucessfully in 2111 ms.
[Server@18b3e62]: Startup sequence completed in 2180 ms.
[Server@18b3e62]: 2004-11-26 01:27:54.522 HSQLDB server 1.7.2 is online
[Server@18b3e62]: To close normally, connect and execute SHUTDOWN SQL
[Server@18b3e62]: From command line, use [Ctrl]+[C] to abort abruptly
- The database 'db' root directory has been set to /disk/raid0/home/vadim/svn/cocoon-2.1.X/build/webapp/WEB-INF/db. Keep in mind that if a war upgrade will take place the database will be lost.
- Database points to /disk/raid0/home/vadim/svn/cocoon-2.1.X/build/webapp/WEB-INF/db
- [main] '/db/system/SysSymbols' Set object system_SysConfig
- [main] '/db/system/SysConfig' Set document database.xml
- [main] '/db/system/SysSymbols' Set object meta_Metas
- [main] '/db/system/SysSymbols' Set object meta_Metas_system_SysConfig
- Database 'db' successfully opened
- Xindice server successfully started
parameter = @PARAMETER@  replaceme = replaceme-abc
parameter = @PARAMETER@  replaceme = replaceme-123
- VM shutting down with the disk store for cocoon-ehcache-1 still active. The disk store is persistent. Calling dispose...
- Database 'db' successfully closed
- Scheduler Cocoon_$_Fri_Nov_26_01:27:43_PST_2004 paused.
- Scheduler Cocoon_$_Fri_Nov_26_01:27:43_PST_2004 shutting down.
- Scheduler Cocoon_$_Fri_Nov_26_01:27:43_PST_2004 paused.
- Scheduler Cocoon_$_Fri_Nov_26_01:27:43_PST_2004 shutdown complete.

Re: Automated Cocoon Unit tests

Posted by Niclas Hedhman <ni...@hedhman.org>.

On Saturday 27 November 2004 09:27, Vadim Gritsenko wrote:
> David Crossley wrote:
> > Hi Vadim, these automated tests that you have
> > are great. Thanks. However i hear that the
> > Infrastructure people are moving all services
> > off "nagoya". So these tests might need to
> > find a new home.
>
> Yes, I know...
>
> > How about asking the Gump people for an account on
> > brutus ... just ask on general@gump.apache.org
>
> And I already asked one of the "Gump people"...
> *cough* Stefano *cough* :)

Technically speaking, you don't need an account on brutus to run tests. You 
just need to manage to set up a Gump descriptor that runs the tests, and have 
it invoked as a project.

Now, there are a few "buts";
1. The Gump folks won't be too happy if the tests takes hour(s). This could 
perhaps be fixed that the Ant script checks for 'time-of'day' and only run 
parts of the tests each time Gump runs.

2. All the dependencies needs to build before the tests will run. At the 
current rate, Cocoon gets very little chance of executing. We used to be at 
93% overall success rate, now down to 72% due to a minute change in Log4J 
affecting velocity, and to test failures in commons-io.
Personally, I start to doubt the scalability of the current Gump strategy, and 
that we probably will need to allow for failures at the low end without 
stopping the builds at the higher up projects.

Cheers
Niclas

-- 
   +------//-------------------+
  / http://www.dpml.net       /
 / http://niclas.hedhman.org / 
+------//-------------------+

Re: Automated Cocoon Unit tests

Posted by Vadim Gritsenko <va...@reverycodes.com>.

David Crossley wrote:
> Hi Vadim, these automated tests that you have
> are great. Thanks. However i hear that the
> Infrastructure people are moving all services
> off "nagoya". So these tests might need to
> find a new home.

Yes, I know...


> How about asking the Gump people for an account on
> brutus ... just ask on general@gump.apache.org

And I already asked one of the "Gump people"...
*cough* Stefano *cough* :)

Vadim

Automated Cocoon Unit tests

Posted by David Crossley <cr...@apache.org>.

Hi Vadim, these automated tests that you have
are great. Thanks. However i hear that the
Infrastructure people are moving all services
off "nagoya". So these tests might need to
find a new home.

How about asking the Gump people for an account on
brutus ... just ask on general@gump.apache.org

http://nagoya.apache.org/~vadim/cocoon/tests/

--David