The change is skipping this test on all architectures, not just s390x.
And it looks like a real failure, at first glance, instead of something
flaky or a race:
1) Bunny::Queue#subscribe provides delivery handler access to message
properties
Failure/Error: expect(metadata.headers["participants"]).to eq 11
expected: 11
got: [11]
(compared using ==)
#
./spec/higher_level_api/integration/message_properties_access_spec.rb:72:in
`block (2 levels) in <top (required)>'
Once a test is being skipped, it's hard to be brought back in... Can you
please file an upstream bug, link it to a launchpad one, so that we have
some hope to put this test back in?
Too bad it's in debian already, there should be a link to this to-be-
filed bug next to the blacklist variable, to track why a test is being
skipped. Maybe you can commit something like that to debian?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873058
Title:
Sync ruby-bunny 2.14.4-3 (universe) from Debian unstable (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-bunny/+bug/1873058/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
