Source: ruby-fission
Version: 0.5.0-2.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-fission failed to build.

Relevant part of the build log (hopefully):
>      Failure/Error: Fission::Action::VM::Stopper.new(self).stop(options)
> 
>        #<Double "vm stopper"> received :stop with unexpected arguments
>          expected: ({:hard=>true}) (keyword arguments)
>               got: ({:hard=>true}) (options hash)
>      # ./lib/fission/vm.rb:135:in `stop'
>      # ./spec/fission/vm_spec.rb:93:in `block (3 levels) in <top (required)>'
> 
> Deprecation Warnings:
> 
> Using `should_receive` 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 
> /<<PKGBUILDDIR>>/spec/fission/action/execute_shell_command_spec.rb:12:in 
> `block (3 levels) in <top (required)>'.
> 
> 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 
> /<<PKGBUILDDIR>>/spec/fission/action/execute_shell_command_spec.rb:18:in 
> `block (3 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.
> 
> 2 deprecation warnings total
> 
> Finished in 0.8034 seconds (files took 0.32206 seconds to load)
> 350 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/fission/vm_spec.rb:51 # Fission::VM start should return a 
> successful response when starting headless
> rspec ./spec/fission/vm_spec.rb:88 # Fission::VM stop should return a 
> successful response when stopping hard
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

Attachment: ruby-fission.log.gz
Description: application/gzip

Attachment: signature.asc
Description: PGP signature

Reply via email to