rabbitfixture 0.5.5

Add support for Python 3.8 to 3.14.

Drop support for Python <3.8.

Add a .launchpad.yaml configuration to run the tests on focal, jammy, noble, and resolute.

No code changes. Only changes to the project and package setup.

Set RABBITMQ_CTL_DIST_PORT_MIN and RABBITMQ_CTL_DIST_PORT_MAX environment variables, as otherwise rabbitmqctl starts this port range at RABBITMQ_DIST_PORT + 10000, which may exceed 65535.

Only send SIGTERM once while stopping RabbitServerRunner, since it’s sent to the whole process group and that can itself interfere with the shutdown process if we send it frequently and repeatedly.

Fix ignoring of ESRCH errors in RabbitServerRunner._signal.

Ignore ESRCH errors in RabbitServerRunner._signal, since this can happen if the server process exits by itself just before we try to signal it.

Add tox testing support and drop buildout.

Fix test_stop_hang failure introduced in 0.4.2.

Handle SIGCHLD while stopping the RabbitServerRunner fixture, since the rabbitmq-server process we’re trying to stop is our direct child process.

Fix ResourceWarning on Python 3 if RabbitServerEnvironment.rabbitctl times out.

Handle new format of rabbitmqctl status output in RabbitMQ 3.7.0.

Allow changing the default server control timeout.

Use a PEP 508 environment marker for the subprocess32 dependency.

Adjust status_regex to cope with removed ellipsis in rabbitmq-server 3.6.10 (https://bugs.launchpad.net/rabbitfixture/+bug/1817642).

Use RABBITMQ_ENABLED_PLUGINS_FILE to disable all plugins (https://bugs.launchpad.net/rabbitfixture/+bug/1817640).

Port to amqp.

Add Python 3 support.

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

Fix buildout no longer working with latest dependency versions.

Fix hang in test_stop_hang unit tests.

Move the kill code into a new RabbitServerRunner.kill API.

Apply a timeout to all rabbitmqctl calls to work around occasional hangs on stop.

Allocate a port for RABBITMQ_DIST_PORT, which is related to clustering in RabbitMQ >= 3.3 (https://bugs.launchpad.net/rabbitfixture/+bug/1322868).

Get the development environment working in Ubuntu 13.04.

Fix port reuse issues when restarting the fixture (https://bugs.launchpad.net/rabbitfixture/+bug/1225980).

Remove RabbitServerResource.tearDown. It was never being called, and is not needed anyway (https://bugs.launchpad.net/rabbitfixture/+bug/847889).

Handle the fixture lifecycle entirely in test_start_check_shutdown (https://bugs.launchpad.net/rabbitfixture/+bug/851813).

Be more flexible when parsing rabbitmqctl status output.

Raise better error messages if rabbit fails to start.

Fix RabbitServerResources reuse by reapplying the defaults each time (potentially setting things back to None, to let them be reallocated).

Use a custom RABBITMQ_PLUGINS_DIR, so the fixture server doesn’t load plugins that might cause port conflicts.

Adjust rabbitmqctl status regex to cope with rabbitmq 2.5.

Make RabbitServerResources configurable so that users have more control over the resources that the fixture makes use of.

Depend on setuptools.

Remove the Launchpad-specific service_config.

Initial release.