FTBFS: port tests to rspec 3 for updating to 1.5.2

Bug #1507415 reported by Logan Rosen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ruby-redis-namespace (Debian)
Fix Released
Unknown
ruby-redis-namespace (Ubuntu)
Triaged
High
Unassigned

Bug Description

Imported from Debian bug http://bugs.debian.org/794359:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

package: ruby-redis-namespce
version: 1.4.1-2
severity: serious

log from pbuilder run with rspec 3, for 1.4.1-2

┌───────────────────────────────────────────────────────────────────────
───────┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
         │
└───────────────────────────────────────────────────────────────────────
───────┘

RUBYLIB=/tmp/buildd/ruby-redis-namespace-1.4.1/debian/ruby-redis-namespa
ce/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
...........F....FF...................FFF........F.......................
.......

Failures:

  1) redis should be able to use a namespace with setbit
     Failure/Error: @namespaced.exists('virgin_key').should be_true
       expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
     # ./spec/redis_spec.rb:119:in `block (2 levels) in <top (required)>
'

  2) redis should be able to use a namespace with mapped_msetnx
     Failure/Error: @namespaced.mapped_msetnx('foo'=>'1000',
'bar'=>'2000').should be_false
       expected false to respond to `false?` or perhaps you meant `be
false` or `be_falsey`
     # ./spec/redis_spec.rb:155:in `block (2 levels) in <top (required)>
'

  3) redis should be able to use a namespace with hashes
     Failure/Error: @namespaced.hsetnx('foonx','nx',10).should be_true
       expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
     # ./spec/redis_spec.rb:176:in `block (2 levels) in <top (required)>
'

  4) redis redis 2.6 commands should namespace bitcount FIXED
     Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
     # ./spec/redis_spec.rb:355

  5) redis redis 2.6 commands should namespace bitop FIXED
     Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
     # ./spec/redis_spec.rb:359

  6) redis redis 2.6 commands should namespace dump FIXED
     Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
     # ./spec/redis_spec.rb:363

  7) redis redis 2.6 commands should namespace restore FIXED
     Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
     # ./spec/redis_spec.rb:410

Deprecation Warnings:

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
/tmp/buildd/ruby-redis-namespace-1.4.1/spec/redis_spec.rb:26:in `block
(2 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.

1 deprecation warning total

Finished in 1.7 seconds (files took 1.83 seconds to load)
79 examples, 7 failures

Failed examples:

rspec ./spec/redis_spec.rb:117 # redis should be able to use a
namespace with setbit
rspec ./spec/redis_spec.rb:153 # redis should be able to use a
namespace with mapped_msetnx
rspec ./spec/redis_spec.rb:161 # redis should be able to use a
namespace with hashes
rspec ./spec/redis_spec.rb:355 # redis redis 2.6 commands should
namespace bitcount
rspec ./spec/redis_spec.rb:359 # redis redis 2.6 commands should
namespace bitop
rspec ./spec/redis_spec.rb:363 # redis redis 2.6 commands should
namespace dump
rspec ./spec/redis_spec.rb:410 # redis redis 2.6 commands should
namespace restore

/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-redis-namespace-1.4.1/debian/ruby-redis-namespace
returned exit code 1
debian/rules:23: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/tmp/buildd/ruby-redis-namespace-1.4.1'
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 2

log for 1.5.2

┌───────────────────────────────────────────────────────────────────────
───────┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
         │
└───────────────────────────────────────────────────────────────────────
───────┘

RUBYLIB=/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-redis-namespac
e/debian/ruby-redis-namespace/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in
`method_missing': undefined method `its' for
RSpec::ExampleGroups::RedisNamespace::Deprecated1XBehaviour:Class
(NoMethodError)
 from
/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-redis-namespace/spec/d
eprecation_spec.rb:20:in
`block (2 levels) in <top (required)>'
 from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
 from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
 from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
 from
/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-redis-namespace/spec/d
eprecation_spec.rb:10:in
`block in <top (required)>'
 from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`module_exec'
 from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in
`subclass'
 from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in
`block in define_example_group_method'
 from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in
expose_example_group_alias'
 from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2
levels) in expose_example_group_alias_globally'
 from
/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-redis-namespace/spec/d
eprecation_spec.rb:5:in
`<top (required)>'
 from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `loa
d'
 from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
 from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `eac
h'
 from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
 from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
 from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
 from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
 from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
 from /usr/bin/rspec:4:in `<main>'
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.1" failed. Exiting.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVvbp/AAoJEM4fnGdFEsIqQcgP/38frAiD50Tb2xtdiJ9zfWoq
3Wp7EUxV7PT6OamSC5zu5L+KmW+WZHZYywjWJfVOv3vfrsqrQ09pTBixoKhCDVcI
HHJmhq/h6uPU1xNupL9NymbP4SUczn310zWORv5KdHBexEfUFIaJ46ZpCVYyzCOh
Cz+DCU6fEpJA2kyBLmDpdeCi77RcDkgjx5w96EUJDSbiJtLgyq5dLIHisvsvV6BA
yHHjOsa+ffNJqdrfC0YKq4vr5DKWm9gPGhwpQqx+U+vw8c0RG3Ffbm5P3LbXS5sg
wxrOXSE3id37jfCaswjM3EaiyxSRSK7uuLDSBigbu31/kj6So7Y5zGCk89U31NPP
IuGX9073/slkwQ6Vx0NrvPC5GcvQ0tCiwNy/grlVks2q+hpYqqReQyOdxzN7Trc8
nlcUCzVI6phwDoD5ZdMQs0/lg4U311Jml7VQfN3gfcB/Hy0bJOsyiQIUqv8Fofxe
eGPp2PJz+ydH23mkht/dsAIhg4/nHgwBnPx/f19+k3aJDpevGlpsinuzWibQHzGr
msq1BF06+GMOaMMRyiV8kU1DABWG8qW1ZeVH5VqTPrX3xWaJDk++OwoRXGVFmKI2
CuhZrA70l490pP1YAq+tYXr+LRa4G9hnGM7+4z7qkuJNcq9RHfXDPeJE4Z0LILYE
QWIHL9X2hZ0L9Q9NOdom
=idjL
-----END PGP SIGNATURE-----

Tags: ftbfs
Logan Rosen (logan)
Changed in ruby-redis-namespace (Ubuntu):
status: New → Triaged
importance: Undecided → High
description: updated
tags: added: ftbfs
Changed in ruby-redis-namespace (Debian):
importance: Undecided → Unknown
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.