Your message dated Sat, 18 Oct 2014 11:58:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#765678: ruby-rack: FTBFS - rake aborted!
has caused the Debian Bug report #765678,
regarding ruby-rack: FTBFS - rake aborted!
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
765678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765678
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ruby-rack
Version: 1.5.2-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
Entering dh_ruby --install
Rewriting shebang line of
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-rack/usr/bin/rackup
Running tests for ruby2.1 using debian/ruby-tests.rake ...
/usr/bin/ruby2.1 /usr/bin/bacon -I./lib:./test -w -a -q -t
'^(?!Rack::Adapter|Rack::Session::Memcache|Rack::Server|Rack::Handler)'
/usr/lib/ruby/vendor_ruby/bacon.rb:221: warning: shadowing outer local variable
- args
/usr/lib/ruby/vendor_ruby/memcache.rb:303: warning: assigned but unused
variable - key_count
/usr/lib/ruby/vendor_ruby/memcache.rb:812: warning: assigned but unused
variable - key
/usr/lib/ruby/vendor_ruby/memcache.rb:24: warning: assigned but unused variable
- e
/usr/lib/ruby/vendor_ruby/continuum_native.rb:38: warning: assigned but unused
variable - e
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/test/spec_webrick.rb:6:in
`<top (required)>': uninitialized constant Rack::Handler::WEBrick (NameError)
from /usr/bin/bacon:116:in `load'
from /usr/bin/bacon:116:in `block in <main>'
from /usr/bin/bacon:115:in `each'
from /usr/bin/bacon:115:in `<main>'
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/test/spec_webrick.rb:6:in
`<top (required)>': uninitialized constant Rack::Handler::WEBrick (NameError)
from /usr/bin/bacon:116:in `load'
from /usr/bin/bacon:116:in `block in <main>'
from /usr/bin/bacon:115:in `each'
from /usr/bin/bacon:115:in `<main>'
.........................................................................................................................................................................................................................
Finished in 0.339649703 seconds.
217 tests, 722 assertions, 0 failures, 0 errors
rake aborted!
Command failed with status (1): [/usr/bin/ruby2.1 /usr/bin/bacon -I./lib:./...]
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-tests.rake:6:in
`block in <top (required)>'
-e:1:in `<main>'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-rack
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.
Best,
Michael
ruby-rack-build-log.txt.gz
Description: application/gunzip
pgpp8FVZ12nLL.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,
[...]
> It does work under sbuild. looking at the source, I understand why it
> would fail, but I don't understand why it doesn't under sbuild. I have
> just uploaded a new version that runs the test suite in verbose mode,
> maybe you can retry on your infrastructure and compare the output, maybe
> it has something to do with the order in which the tests are run, or
> something like that.
>
> I'm attaching the build log on my end.
>
[...]
It seems to work fine now (hence closing), but in case this problem ever occurs
again I'll consult the verbose test logs.
Best,
Michael
pgpSvokRReMDn.pgp
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
