Nope, can't say I like the looks of that.

The test is trying to delete a queue that has a sender blocked on it.   That 
delete command is failing.

I'll try to repo it here.

-K

----- Original Message -----
> From: "Michael Goulish" <mgoul...@redhat.com>
> To: dev@qpid.apache.org
> Sent: Friday, April 26, 2013 12:36:23 PM
> Subject: Re: 0.22 release update - RC2 is available
> 
> Yes!
> 
> From one of the failure-storms, I will just give the
> backtrace form the first failure, since that probably
> caused the others:
> 
> 
> 
> queue_flow_limit_tests.QueueFlowLimitTests.test_blocked_queue_delete ....
> fail
> Error during test:  Traceback (most recent call last):
>     File
>     
> "/home/mick/trunk_22_rc2/qpid/cpp/src/tests/python/commands/qpid-python-test",
>     line 340, in run
>       phase()
>     File
>     "/home/mick/trunk_22_rc2/qpid/cpp/src/tests/queue_flow_limit_tests.py",
>     line 364, in test_blocked_queue_delete
>       self._delete_queue("kill-q")
>     File
>     "/home/mick/trunk_22_rc2/qpid/cpp/src/tests/queue_flow_limit_tests.py",
>     line 87, in _delete_queue
>       self.session.queue_delete(queue=name)
>     File
>     "/home/mick/trunk_22_rc2/qpid/cpp/src/tests/python/qpid/generator.py",
>     line 25, in <lambda>
>       method = lambda self, *args, **kwargs: self.invoke(op, args, kwargs)
>     File "/home/mick/trunk_22_rc2/qpid/cpp/src/tests/python/qpid/session.py",
>     line 138, in invoke
>       return self.do_invoke(op, args, kwargs)
>     File "/home/mick/trunk_22_rc2/qpid/cpp/src/tests/python/qpid/session.py",
>     line 183, in do_invoke
>       self.sync(self.timeout)
>     File "/home/mick/trunk_22_rc2/qpid/cpp/src/tests/python/qpid/session.py",
>     line 101, in sync
>       raise Timeout()
>   Timeout
> 
> 
> 
> 
> 
> ----- Original Message -----
> Hey Mick,
> 
> Any context to the queue flow limit failures?  Error messages/stack trace?
> 
> I think those tests use a shared broker, so one test failure could leave the
> broker in an unknown state and cause all the remaining tests to fail.
> 
> -K
> 
> 
> ----- Original Message -----
> > From: "Michael Goulish" <mgoul...@redhat.com>
> > To: dev@qpid.apache.org
> > Sent: Friday, April 26, 2013 11:49:53 AM
> > Subject: Re: 0.22 release update - RC2 is available
> > 
> > 
> > By the way -- I have no idea what failure percentage for a
> > given test should be judged  GO / NO-GO for a release.
> > 
> > I am only a messenger.
> > 
> > 
> > 
> > :-)
> > 
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> > 
> > I did the autotools "make check" 50 times on an otherwise-deserted
> > RHEL 6.4 box.
> > 
> > Here are the results:
> > 
> > 
> >     qpid_tests.broker_0_10.stats.BrokerStatsTests.test_discards_no_route
> >     {
> >       2 failures
> >     }
> > 
> > 
> >     queue_flow_limit_tests.QueueFlowLimitTests.test_flow_size
> >     {
> >       1 failure
> >       however see below "queue flow limit failure storms"
> >     }
> > 
> > 
> >     queue_flow_limit_tests.QueueFlowLimitTests.test_default_flow_size
> >     {
> >       5 failures
> >       however see below "queue flow limit failure storms"
> >     }
> > 
> > 
> > 
> >     queue flow limit failure storms
> >     {
> >       Twice during the 50 tests, the following
> >       tests all failed one after the other.
> >       ( ? Maybe some shared infrastructure caused all ? )
> > 
> >       queue_flow_limit_tests.QueueFlowLimitTests.test_blocked_queue_delete
> >       queue_flow_limit_tests.QueueFlowLimitTests.test_default_flow_count
> >       queue_flow_limit_tests.QueueFlowLimitTests.test_default_flow_size
> >       queue_flow_limit_tests.QueueFlowLimitTests.test_flow_count
> >       queue_flow_limit_tests.QueueFlowLimitTests.test_flow_size
> >     }
> > 
> > 
> > 
> >     cli_tests.CliTests.test_qpid_config_altex
> >     {
> >       7 times:  Error during teardown
> >     }
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> > Hi, everyone.  RC2 from revision 1470549 is now available:
> > 
> >   http://people.apache.org/~jross/qpid-0.22-rc2/
> >   http://people.apache.org/~jross/qpid-0.22-rc2-testing.txt
> > 
> > My testing (Fedora 16 x86-64, still autotools based) showed no failures.
> > 
> > Since the last update, we decided to add some time between RC1 and
> > RC2.  I expect RC3 to land in one to two weeks, and I feel there's a
> > pretty good chance that RC will represent the GA bits.
> > 
> > So we're getting close.  Please test the RC and report your findings.
> > I'll be sending out candidate release notes this week.
> > 
> > Thanks!
> > Justin
> > 
> > ---
> > 0.22 release page: https://cwiki.apache.org/qpid/022-release.html
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: dev-h...@qpid.apache.org
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: dev-h...@qpid.apache.org
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: dev-h...@qpid.apache.org
> > 
> > 
> 
> --
> -K
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
> 
> 

-- 
-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to