lp:~cjwatson/rabbitfixture/status-no-ellipsis

Created by Colin Watson and last modified
Get this branch:
bzr branch lp:~cjwatson/rabbitfixture/status-no-ellipsis
Only Colin Watson can upload to this branch. If you are Colin Watson please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Colin Watson
Project:
rabbitfixture
Status:
Merged

Recent revisions

41. By Colin Watson

Adjust status_regex to cope with removed ellipsis in rabbitmq-server 3.6.10.

40. By Colin Watson

Release 0.4.0.

39. By Colin Watson

[r=free.ekanayaka] Add Python 3 support.

38. By Gavin Panella

Bump version to 0.3.8.

37. By Free Ekanayaka

Export the RABBITMQ_ENABLED_PLUGINS_FILE environment
variable and make it point to /dev/null by default.

This matches the default value of RABBITMQ_PLUGINS_DIR, which
is currently an empty temporary directory, and prevents
the fixture from failing if the system-wide rabbitmq configuration
has plugins enabled.

36. By Free Ekanayaka

Merge fix-buildout-and-unittests [f=1586779] [r=wgrant]

This branch fixes buildout no longer working with latest eggs. It
upgrades bootstrap.py to the latest version 2 series (from
http://downloads.buildout.org/2/bootstrap.py) and switches buildout.cfg
from z3c.recipe.scripts to zc.recipe.egg.

It also fixes the test_stop_hang unit tests which was failing because
latest versions of the rabbitmq-package (from trusty on) don't spawn
the erlang runtime (which is actually the process listening to the 5672
port) as top-level process, but rather as a child process of
/usr/sbin/rabbitmq-server, which is a shell wrapper. Note that this
is a real fix because the fixture is essentially broken on >=trusty.

Finally it moves the kill code into a new RabbitServerRunner.kill() API so
tests that need to simulate a crash have an handy way to do so.

35. By Colin Watson

Bump version to 0.3.6.

34. By Colin Watson

[r=wgrant] Apply a timeout to all rabbitmqctl calls to work around occasional hangs on stop.

33. By Gavin Panella

Bump version to 0.3.5.

32. By Gavin Panella

[r=jtv][bug=1322868] Allocate a port for RABBITMQ_DIST_PORT, which is related to clustering in RabbitMQ >= 3.3.

Previously RabbitMQ was automatically setting to RABBITMQ_NODE_PORT + 20000, which causes problems when that port is in use, or greater than 2^16.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:rabbitfixture
This branch contains Public information 
Everyone can see this information.

Subscribers