[DRE-maint] Bug#816359: ruby-solve: FTBFS: got #<NoMethodError: undefined method `allow_missing?' for #<Solve::RubySolver:0x00000001df6f00>> with backtrace:
Chris Lamb
lamby at debian.org
Tue Mar 1 07:06:56 UTC 2016
Source: ruby-solve
Version: 2.0.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-builds at lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds at lists.alioth.debian.org
Dear Maintainer,
ruby-solve fails to build from source in unstable/amd64:
[..]
Pending: (Failures listed here are expected and do not affect your suite's status)
1) Solve::GecodeSolver finding unsatisfiable demands partitions demands into satisfiable and not satisfiable
# Not yet implemented
# ./spec/unit/solve/gecode_solver_spec.rb:183
2) Solve ClassMethods #it returns nil if a solution does not exist
# No reason given
# ./spec/unit/solve_spec.rb:8
3) Solve ClassMethods #it! raises NoSolutionError if a solution does not exist
# No reason given
# ./spec/unit/solve_spec.rb:14
Failures:
1) Solutions when using the ruby solver raises NoSolutionError when a solution cannot be found
Failure/Error: lambda {
expected Solve::Errors::NoSolutionError, got #<NoMethodError: undefined method `allow_missing?' for #<Solve::RubySolver:0x00000001df6f00>> with backtrace:
# ./lib/solve/ruby_solver.rb:177:in `resolve_with_error_wrapping'
# ./lib/solve/ruby_solver.rb:72:in `resolve'
# ./lib/solve.rb:64:in `it!'
# ./spec/acceptance/ruby_solver_solutions_spec.rb:36:in `block (3 levels) in <top (required)>'
# ./spec/acceptance/ruby_solver_solutions_spec.rb:35:in `block (2 levels) in <top (required)>'
# ./spec/acceptance/ruby_solver_solutions_spec.rb:35:in `block (2 levels) in <top (required)>'
2) Solutions when using the ruby solver tries all combinations until it finds a solution
Failure/Error: result = Solve.it!(graph, demands)
NoMethodError:
undefined method `allow_missing?' for #<Solve::RubySolver:0x00000001f7b448>
# ./lib/solve/ruby_solver.rb:177:in `resolve_with_error_wrapping'
# ./lib/solve/ruby_solver.rb:72:in `resolve'
# ./lib/solve.rb:64:in `it!'
# ./spec/acceptance/ruby_solver_solutions_spec.rb:201:in `block (2 levels) in <top (required)>'
3) Solve::RubySolver when the constraints are not solvable and molinillo identifies constraints that exclude all known versions raises an error detailing the missing artifacts
Failure/Error: expect(error).to be_a_kind_of(Solve::Errors::NoSolutionError)
expected #<NoMethodError: undefined method `allow_missing?' for #<Solve::RubySolver:0x00000001cbaa38>> to be a kind of Solve::Errors::NoSolutionError
# ./spec/unit/solve/ruby_solver_spec.rb:110:in `block (4 levels) in <top (required)>'
4) Solve::RubySolver when the constraints are not solvable and molinillo identifies missing artifacts raises an error detailing the missing artifacts
Failure/Error: expect(error).to be_a_kind_of(Solve::Errors::NoSolutionError)
expected #<NoMethodError: undefined method `allow_missing?' for #<Solve::RubySolver:0x00000001c5dcc0>> to be a kind of Solve::Errors::NoSolutionError
# ./spec/unit/solve/ruby_solver_spec.rb:90:in `block (4 levels) in <top (required)>'
Deprecation Warnings:
RSpec::Core::Configuration#treat_symbols_as_metadata_keys_with_true_values= is deprecated, it is now set to true as default and setting it to false has no effect.
Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /home/lamby/temp/cdt.20160301070242.8rIosWHgd4/ruby-solve-2.0.1/spec/unit/solve/gecode_solver_spec.rb:68:in `block (2 levels) in <top (required)>'.
Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /home/lamby/temp/cdt.20160301070242.8rIosWHgd4/ruby-solve-2.0.1/spec/unit/solve/gecode_solver_spec.rb:153:in `block (4 levels) in <top (required)>'.
If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.
3 deprecation warnings total
Finished in 0.12653 seconds (files took 0.12439 seconds to load)
105 examples, 4 failures, 3 pending
Failed examples:
rspec ./spec/acceptance/ruby_solver_solutions_spec.rb:31 # Solutions when using the ruby solver raises NoSolutionError when a solution cannot be found
rspec ./spec/acceptance/ruby_solver_solutions_spec.rb:167 # Solutions when using the ruby solver tries all combinations until it finds a solution
rspec ./spec/unit/solve/ruby_solver_spec.rb:109 # Solve::RubySolver when the constraints are not solvable and molinillo identifies constraints that exclude all known versions raises an error detailing the missing artifacts
rspec ./spec/unit/solve/ruby_solver_spec.rb:89 # Solve::RubySolver when the constraints are not solvable and molinillo identifies missing artifacts raises an error detailing the missing artifacts
Randomized with seed 54553
/usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install /home/lamby/temp/cdt.20160301070242.8rIosWHgd4/ruby-solve-2.0.1/debian/ruby-solve returned exit code 1
debian/rules:18: recipe for target 'binary' failed
make: *** [binary] Error 1
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby at debian.org / chris-lamb.co.uk
`-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ruby-solve.2.0.1-2.unstable.amd64.log.txt.gz
Type: application/octet-stream
Size: 2286 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20160301/fb06e0f3/attachment.obj>
More information about the Pkg-ruby-extras-maintainers
mailing list