Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Pirate Praveen]

Control: forwarded -1 https://github.com/celluloid/celluloid-io/issues/180

On Wed, 9 Nov 2016 23:56:59 +0100 (CET) Santiago Vila 
wrote:
> I tried building this package a lot of times today to be sure.
> It failed 14 times out of 50, so it fails approximately of 28% the time.

Disabled the failing tests.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/celluloid/celluloid-io/issues/180
Bug #836595 [src:ruby-celluloid-io] ruby-celluloid-io: FTBFS randomly (failing 
tests)
Set Bug forwarded-to-address to 
'https://github.com/celluloid/celluloid-io/issues/180'.

-- 
836595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Santiago Vila]

On Wed, Nov 09, 2016 at 09:06:26PM +0530, Pirate Praveen wrote:

>  Errno::EADDRINUSE:
>Address already in use - bind(2) for "127.0.0.1" port 12345

Note: I'm not the only one to get those errors.
You can find them in reproducible builds as well:

https://tests.reproducible-builds.org/debian/logs/unstable/amd64/ruby-celluloid-io_0.16.2-2.build2.log.gz

My only recommendation is that each and every test which is known not
to work realiably is just disabled (in addition to forwarding the bug
upstream).

Thanks.

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Santiago Vila]

On Wed, Nov 09, 2016 at 10:41:13PM +0530, Pirate Praveen wrote:

> On 2016, നവംബർ 9 10:22:53 PM IST, Santiago Vila  wrote:
> >I don't think so, because I always build a package at a time.
> 
> Can you try to reproduce it in another setup? May be sbuild on local system.

Just take a look at the build logs I attached to this bug report: It failed
for me on five different autobuilders.

I'm always using sbuild on a single CPU virtual machine. In such setup
the probability of failure seems to be around 20%.

Thanks.

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Pirate Praveen]

On 2016, നവംബർ 9 10:22:53 PM IST, Santiago Vila  wrote:
>I don't think so, because I always build a package at a time.

Can you try to reproduce it in another setup? May be sbuild on local system.

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Santiago Vila]

On Wed, Nov 09, 2016 at 09:06:26PM +0530, Pirate Praveen wrote:
> On Sun, 4 Sep 2016 13:35:32 +0200 (CEST) Santiago Vila 
> wrote:
> 
> All failures have this in common, are you sure other tests (from other
> packages) are not using the same port at the same time?
> 
> 
>  Errno::EADDRINUSE:
>Address already in use - bind(2) for "127.0.0.1" port 12345

I don't think so, because I always build a package at a time.

Thanks.

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Pirate Praveen]

On Sun, 4 Sep 2016 13:35:32 +0200 (CEST) Santiago Vila 
wrote:

All failures have this in common, are you sure other tests (from other
packages) are not using the same port at the same time?


 Errno::EADDRINUSE:
   Address already in use - bind(2) for "127.0.0.1" port 12345



signature.asc
Description: OpenPGP digital signature

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:ruby-celluloid-io
Version: 0.16.2-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:435:in `block in 
with_around_example_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:478:in `block in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:616:in 
`run_around_example_hooks_for'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:478:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:435:in 
`with_around_example_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:478:in 
`with_around_and_singleton_context_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:233:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:581:in `block in 
run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:577:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:577:in 
`run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:543:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:119:in `block (3 levels) 
in run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:119:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:119:in `block (2 levels) 
in run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1680:in 
`with_suite_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:118:in `block in 
run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:77:in `report'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:117:in `run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:93:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:78:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
 # /usr/bin/rspec:4:in `'
 # --
 # --- Caused by: ---
 # IO::EAGAINWaitReadable:
 #   Resource temporarily unavailable - read would block
 #   :76:in `__read_nonblock'

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 
/<>/spec/celluloid/io/tcp_server_spec.rb:14:in `block (5 levels) 
in '.


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 16.67 seconds (files took 0.15227 seconds to load)
230 examples, 1 failure, 2 pending

Failed examples:

rspec ./spec/celluloid/io/reactor_spec.rb:6 # Celluloid::IO::Reactor shouldn't 
crash

Randomized with seed 47642

/usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-celluloid-io 
returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The failure does not seem related to using "dpkg-buildpackage -A".

It does not always fail, but it fails often enough to allow me to
attach 6 different failed build logs to this report.

The builds were made on KVM virtual machines using sbuild and an
up-to-date stretch chroot (plus diffutils 3.5 from unstable, but this
is not the reason it fails), with at least 3 GB of RAM and 4 GB of swap.

BTW: I think the "Randomized with seed xxx" above is a bad idea.
Maintainers often ask bug reporters for "a way to reproduce the error".
But if the build is based on random variables, this becomes an
impossible task. Please consider modifying the build system so that
those random things are always the same.

Thanks.

ruby-celluloid-io_0.16.2-2_amd64-20160904T092219Z.gz
Description: application/gzip


ruby-celluloid-io_0.16.2-2_amd64-20160904T092511Z.gz
Description: application/gzip