On 2016-11-20.22:07, Antonio Terceiro wrote:
> ...
> this update makes the tests of ruby-serverspec fail¹, while it passes on
> current unstable. relevant part of the log:
>
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/type/aix/\*_spec.rb
> ...WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. Called from /tmp/autopkgtest-virt-lxc.shared.0_0jnfgn/downtmp/build.9Hn/ruby-serverspec-2.18.0/spec/type/aix/file_spec.rb:19:in `block (2 levels) in <top (required)>'.
> F.............
>
> Failures:
>
> 1) File "/etc/passwd" be_mode is not implemented
> Failure/Error:
> expect {
> should be_mode 644
> }.to raise_exception
>
> expected Exception but nothing was raised
> # ./spec/type/aix/file_spec.rb:19:in `block (2 levels) in <top (required)>'
>
2.18.0 is quite old. I'll update it and get back to you.
Out of curiosity - do you have a method for running the tests of all
ruby-* packages when updating any one of them? Or did you just run the
serverspec tests because you suspected that a new specinfra might break
them?
--
Regards,
Scott.
Attachment:
signature.asc
Description: Digital signature