[DRE-maint] Bug#795762: only 2 tests fail in pbuilder

Pirate Praveen praveen at debian.org
Mon Oct 5 04:45:55 UTC 2015


/usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/tmp/buildd/ruby-twitter-stream-0.1.16/debian/ruby-twitter-stream/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*/\*_spec.rb

Twitter::JSONStream
  authentication
    should connect with basic auth credentials
    should connect with oauth credentials
  on create
    should return stream
    should define default properties (FAILED - 1)
    should connect to the proxy if provided (FAILED - 2)
    should not trigger SSL until connection is established
  on valid stream
    should add no params
    should add custom params
    should parse headers
    should parse headers even after connection close
    should extract records
    should allow custom headers
    should deliver each item
    should swallow StandardError exceptions when delivering items
    propagates out runtime errors when delivering items
    should send correct user agent
  on network failure
    should timeout on inactivity
    should not reconnect on inactivity when not configured to auto
reconnect
    should reconnect with SSL if enabled
    it should behave like network failure
      should reconnect on network failure
      should not reconnect on network failure when not configured to
auto reconnect
      should reconnect with 0.25 at base
      should reconnect with linear timeout
      should stop reconnecting after 100 times
      should notify after reconnect limit is reached
  on no data received
    should call no data callback after no data received for 90 seconds
  on server unavailable
    it should behave like network failure
      should reconnect on network failure
      should not reconnect on network failure when not configured to
auto reconnect
      should reconnect with 0.25 at base
      should reconnect with linear timeout
      should stop reconnecting after 100 times
      should notify after reconnect limit is reached
  on application failure
    should reconnect on application failure 10 at base
    should not reconnect on application failure 10 at base when not
configured to auto reconnect
    should reconnect with exponential timeout
    should not try to reconnect after limit is reached
  on stream with chunked transfer encoding
    should ignore empty lines
    should parse full entities even if split

Failures:

  1) Twitter::JSONStream on create should define default properties
     Failure/Error: EM.should_receive(:connect).with do |host, port,
handler, opts|
     ArgumentError:
       `with` must have at least one argument. Use `no_args` matcher
to set the expectation of receiving no arguments.
     # ./spec/twitter/json_stream_spec.rb:51:in `block (3 levels) in
<top (required)>'

  2) Twitter::JSONStream on create should connect to the proxy if provided
     Failure/Error: EM.should_receive(:connect).with do |host, port,
handler, opts|
     ArgumentError:
       `with` must have at least one argument. Use `no_args` matcher
to set the expectation of receiving no arguments.
     # ./spec/twitter/json_stream_spec.rb:61: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
/tmp/buildd/ruby-twitter-stream-0.1.16/spec/twitter/json_stream_spec.rb:45: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
/tmp/buildd/ruby-twitter-stream-0.1.16/spec/twitter/json_stream_spec.rb:27: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 24.14 seconds (files took 0.28811 seconds to load)
38 examples, 2 failures

Failed examples:

rspec ./spec/twitter/json_stream_spec.rb:50 # Twitter::JSONStream on
create should define default properties
rspec ./spec/twitter/json_stream_spec.rb:60 # Twitter::JSONStream on
create should connect to the proxy if provided

/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-twitter-stream-0.1.16/debian/ruby-twitter-stream
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
E: Failed autobuilding of package
I: unmounting /home/pravi/forge/debian/pbuilder/ccache filesystem
I: unmounting dev/pts filesystem
W: Could not unmount dev/pts: umount:
/home/pravi/forge/debian/pbuilder/build/5615/dev/pts: not mounted
W: Ignored error in unmount
I: unmounting run/shm filesystem
I: unmounting proc filesystem
I: cleaning the build env
I: removing directory /home/pravi/forge/debian/pbuilder/build/5615 and
its subdirectories



More information about the Pkg-ruby-extras-maintainers mailing list