See <https://builds.apache.org/job/ESME/1127/>
------------------------------------------
[...truncated 198 lines...]
INFO - Service request (DELETE) /api2/session returned 200, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 984 Milliseconds
INFO - Service request (DELETE) /api2/session returned 404, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 3503 Milliseconds
INFO - Service request (GET) /api2/users returned 200, took 12 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 342 Milliseconds
INFO - Service request (GET) /api2/users returned 403, took 8 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 74 Milliseconds
INFO - Service request (POST) /api2/users returned 200, took 704 Milliseconds
INFO - Service request (GET) /api2/users returned 200, took 18 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 351 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 680 Milliseconds
INFO - Service request (POST) /api2/users returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1011 Milliseconds
INFO - Service request (POST) /api2/users returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 366 Milliseconds
INFO - Service request (GET) /api2/users/16/tokens returned 200, took 70
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 132 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 87 Milliseconds
INFO - Service request (GET) /api2/users/2/tokens returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1931 Milliseconds
INFO - Service request (GET) /api2/users/2/tokens returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 547 Milliseconds
INFO - Service request (POST) /api2/users/17/tokens returned 200, took 12
Milliseconds
INFO - Service request (GET) /api2/users/17/tokens returned 200, took 5
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 546 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 782 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens returned 403, took 10
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1119 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 2557 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 519
Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 17
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 898 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 2
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 388 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 4
Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 2
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 183 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 42
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 74 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 47 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 36
Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 6
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 80 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1024 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 3
Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 2011
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 763 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 40 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 377
Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 5
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1906 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 403, took 2
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 3700 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 1077
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 460 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 1016
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 82 Milliseconds
INFO - Service request (GET) /api2/user/followees returned 200, took 22
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1991 Milliseconds
INFO - Service request (GET) /api2/user/followees returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1076 Milliseconds
INFO - Service request (POST) /api2/user/followees returned 200, took 987
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 304 Milliseconds
INFO - Service request (POST) /api2/user/followees returned 403, took 4
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 159 Milliseconds
INFO - Service request (GET) /api2/user/followers returned 200, took 27
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 362 Milliseconds
INFO - Service request (GET) /api2/user/followers returned 403, took 4
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 622 Milliseconds
INFO - Service request (GET) /api2/user/tracks returned 200, took 31
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 2350 Milliseconds
INFO - Service request (GET) /api2/user/tracks returned 403, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1851 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 200, took 13
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 6146 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 403, took 4
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1028 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 200, took 8
Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 returned 200, took 32
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 416 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 returned 403, took 4
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 772 Milliseconds
INFO - Service request (GET) /api2/user/actions returned 200, took 26
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 703 Milliseconds
INFO - Service request (GET) /api2/user/actions returned 403, took 4
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 32137
Milliseconds
INFO - Service request (POST) /api2/user/actions returned 200, took 179
Milliseconds
:12:203: '/' expected instead of ' '
^
INFO - Service request (POST) /api2/session returned 200, took 16417
Milliseconds
INFO - Service request (POST) /api2/user/actions returned 403, took 8
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 111 Milliseconds
INFO - Service request (POST) /api2/user/actions returned 200, took 26
Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 returned 200, took 37
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 173 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 returned 403, took 4
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 75 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 159
Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 151
Milliseconds
INFO - Service request (GET) /api2//conversations/116 returned 200, took 23
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 63 Milliseconds
INFO - Service request (GET) /api2/conversations/1 returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 216 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 returned 404, took 5
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 1091 Milliseconds
INFO - Service request (GET) /api2/pools returned 200, took 25 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 76 Milliseconds
INFO - Service request (GET) /api2/pools returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 275 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 8 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 324 Milliseconds
INFO - Service request (POST) /api2/pools returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 838 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 11 Milliseconds
INFO - Service request (POST) /api2/pools/3/users returned 403, took 16
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 124 Milliseconds
INFO - Service request (POST) /api2/pools/1/users returned 403, took 2
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 115 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 7 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages returned 204, took 7
Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 279
Milliseconds
INFO - Service request (GET) /api2/pools/4/messages returned 200, took 6
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 262 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 4
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 568 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 7
Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 175 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 287
Milliseconds
INFO - Service request (GET) /api2/pools/5/messages returned 200, took 72
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 315 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 93
Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 112
Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 95
Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 180
Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 200, took 31
Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 200, took 15
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 2044 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 3493 Milliseconds
INFO - Service request (POST) /api2/pools returned 403, took 5 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 204, took 3
Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 1612
Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 200, took 10
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 28 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages returned 403, took 2
Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 478
Milliseconds
INFO - Service request (GET) /api2/pools/7/messages returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 564 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 3
Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 574 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 4
Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 2011
Milliseconds
Tests run: 66, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 152.636 sec
<<< FAILURE!
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took
38 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 5
Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 3
Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml returned
200, took 69 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml returned 200,
took 27 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200,
took 37 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml returned 200,
took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200,
took 2 Milliseconds
INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml
returned 200, took 170 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml returned 200, took
20 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml returned 200, took
5 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml returned 200, took
15 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml returned 200, took 8
Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 8
Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200,
took 51 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took
14 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200,
took 38 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml returned
200, took 62 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml
returned 200, took 140 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.043 sec
Running org.apache.esme.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.054 sec
Results :
Failed tests:
StatusNeg(org.apache.esme.api.ApiSpecs$):
Logout(org.apache.esme.api.ApiSpecs$):
LogoutNeg(org.apache.esme.api.ApiSpecs$):
SendMsg(org.apache.esme.api.ApiSpecs$):
SendMsgNeg(org.apache.esme.api.ApiSpecs$):
AddAction(org.apache.esme.api.ApiSpecs$):
AddActionNeg(org.apache.esme.api.ApiSpecs$):
SendMessageToken(org.apache.esme.api.ApiSpecs$):
AddPool(org.apache.esme.api.ApiSpecs$):
AddPoolNeg(org.apache.esme.api.ApiSpecs$):
with valid session(org.apache.esme.api.Api2Specs$):
Tests run: 97, Failures: 11, Errors: 0, Skipped: 0
[ERROR] There are test failures.
Please refer to
<https://builds.apache.org/job/ESME/ws/server/target/surefire-reports> for the
individual test results.
[JENKINS] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[esme-server] in
[<https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4]>
[INFO] Processing war project
[INFO] Copying webapp
resources[<https://builds.apache.org/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[618442 msecs]
[INFO] Building war:
<https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4.war>
[INFO] [install:install {execution: default-install}]
[INFO] Installing
<https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4.war>
to
/export/home/hudson/hudson-slave/maven-repositories/0/org/apache/esme/esme-server/apache-esme-1.4/esme-server-apache-esme-1.4.war
[JENKINS] Archiving <https://builds.apache.org/job/ESME/ws/server/pom.xml> to
/home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2012-11-13_12-45-21/archive/org.apache.esme/esme-server/apache-esme-1.4/esme-server-apache-esme-1.4.pom
[JENKINS] Archiving
<https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4.war>
to
/home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2012-11-13_12-45-21/archive/org.apache.esme/esme-server/apache-esme-1.4/esme-server-apache-esme-1.4.war
Build timed out (after 70 minutes). Marking the build as failed.
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to call isArchivingDisabled. Invalid object ID 5
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalStateException: Unable to call isArchivingDisabled. Invalid
object ID 5
at
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:269)
at
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256)
at
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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:722)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 45 minutes 48 seconds
[INFO] Finished at: Tue Nov 13 13:56:30 GMT+00:00 2012
[INFO] Final Memory: 38M/220M
[INFO] ------------------------------------------------------------------------
Maven failed with error.
channel stopped
[WARNINGS] Skipping publisher since build result is FAILURE
