There are some problems occuring during SVN updates on the Jenkins slaves right now (I just noticed last night for the Java jobs, but I just confirmed the CPP python job is also affected) which could indeed be causing that behaviour as result of a partial update.
We are going to have to clear out the checkouts for all the CI jobs on all the slave nodes, however the Jenkins master node currently needs restarted to resolve a separate problem which is preventing us configuring the jobs to do that. Hopefully someone restarts it later today. Robbie On 27 June 2012 15:22, Gordon Sim <[email protected]> wrote: > On 06/27/2012 10:01 AM, Gordon Sim wrote: >> >> On 06/26/2012 11:34 AM, Gordon Sim wrote: >>> >>> On 06/26/2012 09:51 AM, Keith W wrote: >>>> >>>> Hello >>>> >>>> I noticed this morning that the new python tests added by QPID-4075 >>>> failed >>>> on the Python/Cpp job on Apache CI. >>>> >>>> https://builds.apache.org//view/M-R/view/Qpid/job/Qpid-Python-Cpp-Test/ >>>> >>>> I see that the tests had passed a couple of times since the original >>>> commit, which may suggest a reliablity issue somewhere. >>> >>> >>> Thanks for pointing that out. I've increased the timeout and will keep >>> an eye on the results to see if that addresses it. >> >> >> Apparently not... failed again this morning. I've run the event tests in >> a loop for hours (on both single and multi core boxes) with not a single >> glitch, so I'm a bit baffled as to the failure. I will see what else I >> can discover however. > > > I suspect the issue here to be that the tests are running against an old(er) > broker. The three failing tests (2 event generation tests, 1 reroute test) > are the last three to be modified and the failures are symptomatic of the > functionality not being in the broker, i.e. of the the broker being based on > a revision older than r1350003. > > Is there anyway to check that? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
