Austin, maybe the best answer is to declare the RabbitMQ version dependency at https://github.com/numenta/numenta-apps/tree/master/htmengine#requirements or on the nta.utils readme? https://github.com/numenta/numenta-apps/blob/master/nta.utils/README.md --------- Matt Taylor OS Community Flag-Bearer Numenta
On Mon, Aug 10, 2015 at 11:12 PM, Francesco Cristofori <[email protected]> wrote: > Hi Austin! > > Thank you for the hint on the rabbitmq version , this was the cause of the > error. > > For future reference here is what I did : > > 1) Installed rabbitmq-server from Debian Jessie repositories (3.3.x version) > 2) wget the rabbitmq-server_3.5.4-1_all.deb from stretch repository > 3) dpkg -i rabbitmq-server_3.5.4-1_all.deb > > Tests went good : > debtest:/home/fracrist/numenta/numenta-apps/nta.utils# py.test > tests/integration/ > ============================================================================================= > test session starts > ============================================================================================= > platform linux2 -- Python 2.7.9 -- pytest-2.4.2 > plugins: xdist, cov > collected 44 items > > tests/integration/message_bus_connector_test.py ........................... > tests/integration/synchronous_amqp_client_test.py ................. > > ========================================================================================= > 44 passed in 60.29 seconds > ========================================================================================== > debtest:/home/fracrist/numenta/numenta-apps/nta.utils# > > I think this doesn't worth a git issue, but if you prefer I will open it > anyway. > > Thanks, > Francesco. > >> Hi Francesco! >> >> Would you mind creating an issue at >> https://github.com/numenta/numenta-apps/issues/new with the steps to >> reproduce and the output of the command that fails? >> >> One thing to consider: One of the tests uses the http json api, which >> differs in older versions of rabbitmq and could explain the error message >> you're reporting -- it's hard to tell without the full context. I suspect >> you're on a 3.3.x version. I recommend updating to a recent version of >> rabbitmq (3.5.x), and to try again.
