The last run being 2 days ago is just reflective of the few properly functioning Jenkins nodes currently being overloaded with jobs. It has passed on the several previous CPP profile runs on Jenkins, e.g: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1341/testReport/org.apache.qpid.client/SessionCreateTest/
There are some cases it was rather slow though, but that could just be from running on one of the poorly Jenkins nodes: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1338/testReport/org.apache.qpid.client/SessionCreateTest/ This JIRA was raised some time ago due to the test being really slow, though it was only noticed on the SSL profile: https://issues.apache.org/jira/browse/QPID-3431 Are you sure it has actually hung? Do you have any local changes, and does it work without them? The test doesn't look to have failed in any of the build results on record for the last 2 weeks, and the last change to the client was 3 weeks ago: http://svn.apache.org/r1463158 It isn't actually running at all on the Java broker profiles: java/test-profiles/JavaExcludes:org.apache.qpid.client.SessionCreateTest#* Robbie On 22 April 2013 20:30, Rajith Attapattu <[email protected]> wrote: > Hi Folks, > > org.apache.qpid.client.SessionCreateTest hangs when I run its under the cpp > profile. > It works well under the java broker profile. > > It seems the last successful run on Jenkins was 2 days ago > > https://builds.apache.org/job/Qpid-Java-Cpp-Test/ > > Anybody else seeing this ? > > Regards, > > Rajith >
