Your message dated Mon, 20 Nov 2017 16:42:11 +0100
with message-id <20171120154211.3wog23nnnildvkx4@shiraz>
and subject line transitive bug
has caused the Debian Bug report #841133,
regarding ruby-gruff: FTBFS: Tests hang after segmentation fault
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.)
--
841133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841133
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-gruff
Version: 0.6.0-1
Severity: serious
Justification: fails to build from source
User: [email protected]
Usertags: ftbfs
X-Debbugs-Cc: [email protected]
Dear Maintainer,
ruby-gruff fails to build from source in unstable/amd64:
[…]
/usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:65:in `run_suite'
/usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
/usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
/usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
/usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
/usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
/usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
/usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `run'
/usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `catch'
/usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:468:in `block in run'
/usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:283:in `run_setup'
/usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:248:in `run_fixture'
/usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in
create_fixtures_runner'
/usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in
create_fixtures_runner'
/usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:470:in `block (2 levels) in
run'
/usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:744:in `run_test'
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
`test_bezier'
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
`new'
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:230:in
`initialize'
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
`reset_themes'
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
`new'
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
`initialize'
-- Machine register context ------------------------------------------------
RIP: 0x00007f59938d0249 RBP: 0x0000000000000000 RSP: 0x00007ffd0ad90bd0
RAX: 0x0000000000000000 RBX: 0x0000000001ee7510 RCX: 0x0000000000000021
RDX: 0x0000000000000000 RDI: 0x00007f5993bf1b00 RSI: 0x0000000000000000
R8: 0x0000000001ee7520 R9: 0x00000000000041a0 R10: 0x0000000000000000
R11: 0x0000000000000000 R12: 0x00007f5993bf1b58 R13: 0x00007f5993bf1b18
R14: 0x0000000001ee7510 R15: 0x00007f5993bf1b00 EFL: 0x0000000000010246
[…]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
ruby-gruff.0.6.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Hi,
according to ci.debian.org, the package has been usable since Jan 1,
2017 after a long period of failure, matching the date of the bug
report.
I could build it here locally without problem and the problem mentioned
by Gunnar isn't showing up.
It was probably a bug triggered by a dependency, updated in the mean
time.
I am therefore closing this bug.
Cheers,
Cédric
signature.asc
Description: PGP signature
--- End Message ---
