The autopkgtest failures [1] on this seem unrelated as they are failing
to importoslo.versionedobjects and there is no oslo found. This same
failure occurs on python-oslo.versionedobjects without using the new
python-oslo.messaging from proposed and a later (Groovy) version of
python-oslo.versionedobjects has updated debian/tests/python-import to
handle the import differently; specifically, the Bionic version is:
set -e
for py in $(py3versions -r 2>/dev/null) ; do
cd "$AUTOPKGTEST_TMP"
echo "Testing with $py:"
$py -c "import oslo.versionedobjects; print(oslo.versionedobjects)"
done
and the Groovy version is:
#!/bin/sh
set -e
MODULE_NAME=$(python3 setup.py --name | sed 's/\./_/g')
for py in $(py3versions -r 2>/dev/null) ; do
cd "$AUTOPKGTEST_TMP"
echo "Testing with $py:"
$py -c "import $MODULE_NAME; print($MODULE_NAME)"
done
The big difference to call out is that the groovy version replaces the
dot ('.') after oslo with an underscore for the module import.
[1]: https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#python-oslo.messaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789177
Title:
RabbitMQ fails to synchronize exchanges under high load
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
