[Bug 1873058] Re: Sync ruby-bunny 2.14.4-3 (universe) from Debian unstable (main)

[Andreas Hasenack]

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
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1873058

Title:
  Sync ruby-bunny 2.14.4-3 (universe) from Debian unstable (main)

Status in ruby-bunny package in Ubuntu:
  New

Bug description:
  Please sync ruby-bunny 2.14.4-3 (universe) from Debian unstable (main)

  This revision will fix a ruby-bunny regression in s390x. After a discussion
  with one of the maintainers the way to go now is skipping this specific failing
  test.

  Changelog entries since current focal version 2.14.4-2:

  ruby-bunny (2.14.4-3) unstable; urgency=medium

    * Team upload
    * d/ruby-tests.rake: skip a test consistently failing in s390x
    * d/control: use secure url in Homepage field

   -- Lucas Kanashiro <lucas.kanashiro at canonical.com>  Wed, 15 Apr 2020
  10:04:15 -0300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-bunny/+bug/1873058/+subscriptions