Robbie, thanks for checking this out. In my case the test appeared hung for a considerable time, after which the test timed out. My recollection is that this test used to get through a lot quicker. The 90secs you mentioned is more like it.
Maybe we should look at modifying the test to make it more reasonable than excluding it. Thanks again for checking this out. Rajith On Mon, Apr 22, 2013 at 6:33 PM, Robbie Gemmell <robbie.gemm...@gmail.com>wrote: > I'm still a little unclear on whether you actually saw the test suite > complete/abort (due to the timelimit on the JUnit test run) with a failure > or not? This particular test does the same thing over and over again, so > are you sure it isn't just going [very] slowly and hasn't finished yet? > (Possibly instrument the test and see, or increase the JUnit timeout?) > > As far as I'm aware it is passing in the other CI environment I use to run > the C++ profile, yes. I would expect it to pass the next time it runs on > the ASF Jenkins nodes given it hasn't been failing previously and there > have been no client changes in weeks to suggest it should now. > > When was the last time you successfully ran the C++ profile on the machine? > Although it doesn't appear like a particular change has caused any issue, > have you tried reverting the codebase to an earlier timeframe you know > worked and running the test again? > > As mentioned, the test is excluded on all the Java broker profiles so it > isn't actually passing there (though you could remove the exclude and check > if it does). It has been excluded since the day it was committed, because > "this takes ages to run". It was also excluded from the C++ profiles at the > same time, but that has obviously changed at some point over the years. > > Robbie > > On 22 April 2013 23:07, Rajith Attapattu <rajit...@gmail.com> wrote: > > > There are no local changes. I initially came across this when testing > out a > > patch on a branch. > > After that, I moved back to trunk, made sure I have the latest and no > local > > changes. > > From the stack trace below it appears to be hung on a timed wait. But why > > it doesn't time out beats me. > > > > It certainly looks strange, hence the reason why I wanted to reach out > and > > see if others are also noticing this. > > This can be reproduced (on my machine every time I run the build). > > > > "main" prio=10 tid=0x00007f3d1c011000 nid=0xd54 in Object.wait() > > [0x00007f3d21c85000] > > [junit] java.lang.Thread.State: TIMED_WAITING (on object monitor) > > [junit] at java.lang.Object.wait(Native Method) > > [junit] at > > org.apache.qpid.transport.util.Waiter.await(Waiter.java:54) > > [junit] at > > org.apache.qpid.transport.Session.awaitClose(Session.java:1067) > > [junit] at > > org.apache.qpid.transport.Session.close(Session.java:1056) > > > > Does this test pass on your env? > > The fact that it pass with the java profile and fails consistently with > the > > cpp profile is interesting. > > I will try this out on a different env tomorrow and see what happens. > > Meanwhile I hope we get a jenkins run going or someone else had run it on > > their local machine. > > > > Rajith > > > > > > On Mon, Apr 22, 2013 at 5:42 PM, Robbie Gemmell < > robbie.gemm...@gmail.com > > >wrote: > > > > > 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 <rajit...@gmail.com> 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 > > > > > > > > > >
