Hi all, As per https://issues.apache.org/jira/browse/QPID-3587, a number of the Python based broker tests currently fail when run against the Java broker because they depend on the differing behaviour of the C++ broker when it comes to counting the number of messages on the queue. The Java broker includes acquired messages in its counts because it still considers them to be on the queue (because they are), whereas it seems the C++ broker removes them from its counts. If the tests are modified to expect the Java brokers behaviour then they pass against the Java broker, but obviously would then fail against the C++ broker.
It would be good to get these tests running against the Java broker so that we can actually discover if they ever legitimately begin failing due to changes that have been made. We could add 'if includeAcquired else' behaviour to the tests but it would be nice to avoid that if possible. I saw mention on a JIRA of the C++ broker possibly adopting the behaviour used by the Java broker in future, and wondered if there are there actually solid plans to do this in the near'ish future, or whether we should instead just look to modify the tests now to allow for either behaviour? Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
