Cool, I'm guessing by 'build every build' you mean build and run tests on every build. So can you tell what change broke the Java broker. I run all the java test on a regular basis I just keep forgetting the python ones, though I was good and remembered for a while. I have it on my list to integrate the running of the tests with maven but it is a little more tricky when running under windows with cygwin.
I forgot I'm actually on holiday today (moving house) so may not get much time to track down the cause of the three test failures. Would be good to know how long the QueueTests.test_purge has been failing. On 15/05/07, Carl Trieloff <[EMAIL PROTECTED]> wrote:
Martin, We build every check in on the source tree, I will see if we can link the page externally. Also does anyone mind if that machine auro mails the list with build failures / blame. Carl. Martin Ritchie wrote: > oh dear Qpid java people, > > We have been caught committing and not running the python tests. > > I say we as I'm probably the culprit but running the test after > finally putting a topic matching solution in.. Thinking we would be > fully passing the python tests only to find we have three new > failures. > > One I think I introduced recently (Basic.test_get) but the test_purge > looks as though it has been broken for a while and I can't think of > what could have changed since we were last caught out for not running > the python tests and made the effort to get them all running again. > > I shall be looking at them again tomorrow but if anyone has an idea > why these guys might have started failing: > tests.basic.BasicTests.test_consume_exclusive > tests.basic.BasicTests.test_get > tests.queue.QueueTests.test_purge > > Then feel free to chime in, while I sleep on the issue. > > ttfn
-- Martin Ritchie
