Your message dated Mon, 28 Mar 2022 20:49:55 +0200
with message-id <4aec0557-ff49-efa3-2ddd-6f715c972...@debian.org>
and subject line Re: ruby-hamster: autopkgtest regression: output differ
has caused the Debian Bug report #1005032,
regarding ruby-hamster: autopkgtest regression: output differ
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1005032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-hamster
Version: 3.0.0-4
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of ruby-hamster the autopkgtest of ruby-hamster
fails in testing when that autopkgtest is run with the binary packages
of ruby-hamster from unstable. It passes when run with only packages
from testing. In tabular form:
pass fail
ruby-hamster from testing 3.0.0-4
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=ruby-hamster
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-hamster/18964952/log.gz
Failures:
1) Hamster.to_ruby with Hamster::SortedSet[] as input should return
::SortedSet.new
Failure/Error: Hamster.to_ruby(Hamster::SortedSet[]).should ==
::SortedSet.new
expected: #<SortedSet: {}>
got: #<SortedSet: {}> (using ==)
# ./spec/lib/hamster/nested/construction_spec.rb:85:in `block (4
levels) in <top (required)>'
Finished in 13.72 seconds (files took 1.56 seconds to load)
4593 examples, 1 failure, 10 pending
Failed examples:
rspec ./spec/lib/hamster/nested/construction_spec.rb:84 #
Hamster.to_ruby with Hamster::SortedSet[] as input should return
::SortedSet.new
/usr/bin/ruby2.7
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
--pattern ./spec/\*\*/\*_spec.rb --format documentation failed
mv ./.gem2deb.lib lib
autopkgtest [07:11:17]: test gem2deb-test-runner
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi
On Sat, 5 Feb 2022 21:24:22 +0100 Paul Gevers <elb...@debian.org> wrote:
With a recent upload of ruby-hamster the autopkgtest of ruby-hamster
fails in testing when that autopkgtest is run with the binary packages
of ruby-hamster from unstable. It passes when run with only packages
from testing.
Apparently somewhere between 3 March and 4 March, this changed in
testing (around the same time that ruby-defaults migrated). The test now
passes, but technically it means that a *versioned* (test) dependency
was missing.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
