You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Apache Hudson Server <hu...@hudson.apache.org> on 2011/03/16 13:39:00 UTC

Build failed in Jenkins: ESME #533

See <https://hudson.apache.org/hudson/job/ESME/533/changes>

Changes:

[rhirsch] [ESME-340] General Task to perform release associated tasks

[rhirsch] [ESME-338] Follow / unfollow messages should contain links
Patch from Vladimir Ivanov

------------------------------------------
[...truncated 283 lines...]
INFO - Service request (POST) /api2/user/tracks took 14 Milliseconds
INFO - Service request (POST) /api2/session took 17 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 2 Milliseconds
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 took 26 Milliseconds
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 17 Milliseconds
INFO - Service request (GET) /api2/user/actions took 19 Milliseconds
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (GET) /api2/user/actions took 3 Milliseconds
INFO - Service request (POST) /api2/session took 24 Milliseconds
INFO - Service request (POST) /api2/user/actions took 48 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/user/actions took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/user/actions took 16 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 took 35 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/user/messages took 19 Milliseconds
INFO - Service request (POST) /api2/user/messages took 64 Milliseconds
INFO - Service request (GET) /api2//conversations/92 took 17 Milliseconds
INFO - Service request (POST) /api2/session took 19 Milliseconds
INFO - Service request (GET) /api2/conversations/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 24 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 took 5 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (GET) /api2/pools took 21 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (GET) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 15 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/pools/3/users took 36 Milliseconds
INFO - Service request (POST) /api2/session took 17 Milliseconds
INFO - Service request (POST) /api2/pools/1/users took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 7 Milliseconds
:12:209: '/' expected instead of ' '

                                                                                                                                                                                                                ^
INFO - Service request (POST) /api2/user/messages took 57 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 21 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 15 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 2 Milliseconds
INFO - Service request (POST) /api2/session took 15 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages took 18 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 60 Milliseconds
INFO - Service request (POST) /api2/session took 25 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (POST) /api2/user/messages took 21 Milliseconds
INFO - Service request (POST) /api2/user/messages took 25 Milliseconds
INFO - Service request (POST) /api2/user/messages took 24 Milliseconds
INFO - Service request (POST) /api2/user/messages took 22 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 26 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 51 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 15 Milliseconds
INFO - Service request (POST) /api2/pools took 4 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 20 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 7 Milliseconds
INFO - Service request (POST) /api2/session took 19 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 19 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/session took 17 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 15 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 2003 Milliseconds
Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.586 sec
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login took 37 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 3 Milliseconds
INFO - Service request (POST) /api/login took 3 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 20 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 18 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (GET) /api/logout took 5 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (POST) /api/login took 16 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (POST) /api/login took 21 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/send_msg took 5 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/login took 15 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/login took 15 Milliseconds
INFO - Service request (POST) /api/add_action took 19 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 16 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 8 Milliseconds
INFO - Service request (POST) /api/add_action took 11 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt took 7 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/login took 17 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/send_msg took 4 Milliseconds
Full(<esme_api success="true"><xml:group></xml:group></esme_api>)
INFO - Service request (POST) /api/login took 20 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt87 took 6 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 2 Milliseconds
INFO - Service request (POST) /api/login took 15 Milliseconds
INFO - Service request (POST) /api/add_pool took 15 Milliseconds
INFO - Service request (POST) /api/send_msg took 1 Milliseconds
INFO - Service request (POST) /api/send_msg took 1 Milliseconds
Full(<esme_api msg="message parameter is missing" success="false"><xml:group></xml:group></esme_api>)
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.034 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.022 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml took 39 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 4 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 2 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 64 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 25 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 34 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 1 Milliseconds
INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml took 34 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 15 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 4 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 21 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 6 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 5 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 21 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 9 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 53 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 46 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml took 52 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.597 sec

Results :

Tests run: 118, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[esme-server] in [<https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2]>
[INFO] Processing war project
[INFO] Copying webapp resources[<https://hudson.apache.org/hudson/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[1182 msecs]
[INFO] Building war: <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war>
[INFO] [install:install {execution: default-install}]
[INFO] Installing <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /home/hudson/.m2/repository/org/apache/esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
[JENKINS] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/pom.xml> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-03-16_12-32-38/archive/org.apache.esme/esme-server/apache-esme-1.2/pom.xml
[JENKINS] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-03-16_12-32-38/archive/org.apache.esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 minutes 53 seconds
[INFO] Finished at: Wed Mar 16 05:38:59 PDT 2011
[INFO] Final Memory: 40M/283M
[INFO] ------------------------------------------------------------------------
ERROR: Processing failed due to a bug in the code. Please report this to jenkins-users@googlegroups.com
java.lang.ClassCastException: cannot assign instance of hudson.FilePath to field hudson.plugins.violations.ViolationsCollector.htmlDir of type hudson.FilePath in instance of hudson.plugins.violations.ViolationsCollector
	at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2056)
	at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1229)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1969)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
	at hudson.remoting.UserRequest.deserialize(UserRequest.java:178)
	at hudson.remoting.UserRequest.perform(UserRequest.java:98)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)
project=hudson.maven.MavenModuleSet@3cd16610[ESME]
project.getModules()=[hudson.maven.MavenModule@26bb2f6e[ESME/org.apache.esme:esme-server][ESME/org.apache.esme:esme-server][relativePath:]]
project.getRootModule()=hudson.maven.MavenModule@26bb2f6e[ESME/org.apache.esme:esme-server][ESME/org.apache.esme:esme-server][relativePath:]
FATAL: cannot assign instance of hudson.FilePath to field hudson.plugins.violations.ViolationsCollector.htmlDir of type hudson.FilePath in instance of hudson.plugins.violations.ViolationsCollector
java.lang.ClassCastException: cannot assign instance of hudson.FilePath to field hudson.plugins.violations.ViolationsCollector.htmlDir of type hudson.FilePath in instance of hudson.plugins.violations.ViolationsCollector
	at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2056)
	at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1229)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1969)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
	at hudson.remoting.UserRequest.deserialize(UserRequest.java:178)
	at hudson.remoting.UserRequest.perform(UserRequest.java:98)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)


Jenkins build is back to normal : ESME #535

Posted by Apache Hudson Server <hu...@hudson.apache.org>.
See <https://hudson.apache.org/hudson/job/ESME/535/>



Build failed in Jenkins: ESME #534

Posted by Apache Hudson Server <hu...@hudson.apache.org>.
See <https://hudson.apache.org/hudson/job/ESME/534/>

------------------------------------------
[...truncated 275 lines...]
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 2 Milliseconds
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 took 26 Milliseconds
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (GET) /api2/user/actions took 19 Milliseconds
INFO - Service request (POST) /api2/session took 24 Milliseconds
INFO - Service request (GET) /api2/user/actions took 3 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/user/actions took 48 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/user/actions took 3 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/user/actions took 17 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 took 36 Milliseconds
INFO - Service request (POST) /api2/session took 17 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/user/messages took 20 Milliseconds
INFO - Service request (POST) /api2/user/messages took 58 Milliseconds
INFO - Service request (GET) /api2//conversations/92 took 17 Milliseconds
INFO - Service request (POST) /api2/session took 24 Milliseconds
INFO - Service request (GET) /api2/conversations/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 18 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 took 4 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (GET) /api2/pools took 21 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (GET) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/pools/3/users took 36 Milliseconds
INFO - Service request (POST) /api2/session took 17 Milliseconds
INFO - Service request (POST) /api2/pools/1/users took 2 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 7 Milliseconds
:12:209: '/' expected instead of ' '

                                                                                                                                                                                                                ^
INFO - Service request (POST) /api2/user/messages took 27 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 15 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 15 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages took 20 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 98 Milliseconds
INFO - Service request (POST) /api2/session took 21 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages took 23 Milliseconds
INFO - Service request (POST) /api2/user/messages took 24 Milliseconds
INFO - Service request (POST) /api2/user/messages took 25 Milliseconds
INFO - Service request (POST) /api2/user/messages took 28 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 24 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 25 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 4 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 20 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 7 Milliseconds
INFO - Service request (POST) /api2/session took 30 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 25 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/session took 25 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 17 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 2002 Milliseconds
Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.392 sec
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login took 30 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 3 Milliseconds
INFO - Service request (POST) /api/login took 3 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 22 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 19 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (POST) /api/login took 63 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (POST) /api/login took 14 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (POST) /api/send_msg took 6 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/login took 16 Milliseconds
INFO - Service request (POST) /api/send_msg took 3 Milliseconds
INFO - Service request (POST) /api/login took 15 Milliseconds
INFO - Service request (POST) /api/add_action took 19 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 7 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 6 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 17 Milliseconds
INFO - Service request (POST) /api/add_action took 11 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 12 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt took 8 Milliseconds
INFO - Service request (POST) /api/add_action took 11 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/login took 16 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/send_msg took 10 Milliseconds
Full(<esme_api success="true"><xml:group></xml:group></esme_api>)
INFO - Service request (POST) /api/login took 17 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt87 took 5 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 2 Milliseconds
INFO - Service request (POST) /api/login took 16 Milliseconds
INFO - Service request (POST) /api/add_pool took 23 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/send_msg took 1 Milliseconds
Full(<esme_api msg="message parameter is missing" success="false"><xml:group></xml:group></esme_api>)
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.996 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.022 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml took 34 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 4 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 67 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 42 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 41 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 2 Milliseconds
INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml took 33 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 15 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 4 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 13 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 7 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 6 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 23 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 6 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 50 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 60 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml took 47 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.414 sec

Results :

Tests run: 118, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[esme-server] in [<https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2]>
[INFO] Processing war project
[INFO] Copying webapp resources[<https://hudson.apache.org/hudson/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[1119 msecs]
[INFO] Building war: <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war>
[INFO] [install:install {execution: default-install}]
[INFO] Installing <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /home/hudson/.m2/repository/org/apache/esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
[JENKINS] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/pom.xml> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-03-17_12-13-25/archive/org.apache.esme/esme-server/apache-esme-1.2/pom.xml
[JENKINS] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-03-17_12-13-25/archive/org.apache.esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 minutes 57 seconds
[INFO] Finished at: Thu Mar 17 05:19:48 PDT 2011
[INFO] Final Memory: 40M/284M
[INFO] ------------------------------------------------------------------------
Waiting for Jenkins to finish collecting data
ERROR: Processing failed due to a bug in the code. Please report this to jenkins-users@googlegroups.com
java.lang.ClassCastException: cannot assign instance of hudson.FilePath to field hudson.plugins.violations.ViolationsCollector.htmlDir of type hudson.FilePath in instance of hudson.plugins.violations.ViolationsCollector
	at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2056)
	at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1229)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1969)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
	at hudson.remoting.UserRequest.deserialize(UserRequest.java:178)
	at hudson.remoting.UserRequest.perform(UserRequest.java:98)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)
project=hudson.maven.MavenModuleSet@3cd16610[ESME]
project.getModules()=[hudson.maven.MavenModule@26bb2f6e[ESME/org.apache.esme:esme-server][ESME/org.apache.esme:esme-server][relativePath:]]
project.getRootModule()=hudson.maven.MavenModule@26bb2f6e[ESME/org.apache.esme:esme-server][ESME/org.apache.esme:esme-server][relativePath:]
FATAL: cannot assign instance of hudson.FilePath to field hudson.plugins.violations.ViolationsCollector.htmlDir of type hudson.FilePath in instance of hudson.plugins.violations.ViolationsCollector
java.lang.ClassCastException: cannot assign instance of hudson.FilePath to field hudson.plugins.violations.ViolationsCollector.htmlDir of type hudson.FilePath in instance of hudson.plugins.violations.ViolationsCollector
	at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2056)
	at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1229)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1969)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
	at hudson.remoting.UserRequest.deserialize(UserRequest.java:178)
	at hudson.remoting.UserRequest.perform(UserRequest.java:98)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)