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:
(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?
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 metadata. headers[ "participants" ]).to eq 11
Failure/Error: expect(
expected: 11
got: [11]
(compared using ==) higher_ level_api/ integration/ message_ properties_ access_ spec.rb: 72:in `block (2 levels) in <top (required)>'
# ./spec/
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?