Your message dated Mon, 4 Jun 2012 18:57:20 -0300
with message-id <[email protected]>
and subject line ruby1.9.1 does not FTBFS on kfreebsd, ia64 and kfreebsd-*
anymore
has caused the Debian Bug report #593139,
regarding ruby1.9.1: FTBFS on kfreebsd: test suite segfaults
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.)
--
593139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593139
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby1.9.1
Version: 1.9.2~svn28788-1
Severity: serious
Ruby's test suite fails on kfreebsd-i386 and kfreebsd-amd64, and then hangs.
i386:
> Loaded suite ./test/runner
> Started
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/lib/timeout.rb:50:
> [BUG] Segmentation fault
> ruby 1.9.2dev (2010-07-30) [i486-kfreebsd-gnu]
>
> -- control frame ----------
> c:0004 p:---- s:0011 b:0011 l:000010 d:000010 CFUNC :sleep
> c:0003 p:0014 s:0007 b:0007 l:001950 d:000006 BLOCK
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/lib/timeout.rb:50
> c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
> c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP
> ---------------------------
> -- Ruby level backtrace information ----------------------------------------
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/lib/timeout.rb:50:in
> `block in timeout'
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/lib/timeout.rb:50:in
> `sleep'
>
> -- C level backtrace information -------------------------------------------
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(rb_vm_bugreport+0x72)
> [0x281c30e2]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x4fb41)
> [0x280beb41]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(rb_bug+0x3a)
> [0x280bebda]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0xee61c)
> [0x2815d61c]
> /lib/libpthread.so.0(+0xaaa7) [0x28243aa7]
> [0xbfbfffb4]
> /lib/libpthread.so.0(__pthread_mutex_unlock+0x9f) [0x2823f8af]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x15493a)
> [0x281c393a]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x156bcc)
> [0x281c5bcc]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x158214)
> [0x281c7214]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0xb89ed)
> [0x281279ed]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x13e948)
> [0x281ad948]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x14cb12)
> [0x281bbb12]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x1443f2)
> [0x281b33f2]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x14a528)
> [0x281b9528]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(rb_vm_invoke_proc+0x29c)
> [0x281bb5cc]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x1595bd)
> [0x281c85bd]
> /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9(+0x15961b)
> [0x281c861b]
> /lib/libpthread.so.0(+0x570c) [0x2823e70c]
> /lib/libc.so.0.1(+0xc6768) [0x28380768]
amd64:
> Loaded suite ./test/runner
> Started
> Bus error
> make[1]: *** [yes-test-all] Error 138
> .................................................................................................................................
> make[1]: Leaving directory
> `/build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-amd64-Etillu/ruby1.9.1-1.9.2~svn28788'
> make: [common-post-build-arch] Error 2 (ignored)
Also, on both i386 and amd64, there are many new failures in the first test
suite (ruby includes one called "make test", the second one being "make
test-all"): 49/922 tests failed on both i386 and amd64. (search for "undefined
method `signaled?' for nil:NilClass" in the build log).
Full build logs:
https://buildd.debian.org/fetch.cgi?pkg=ruby1.9.1;ver=1.9.2~svn28788-1;arch=kfreebsd-i386;stamp=1280703210
https://buildd.debian.org/fetch.cgi?pkg=ruby1.9.1;ver=1.9.2~svn28788-1;arch=kfreebsd-amd64;stamp=1280661492
There's an history of kfreebsd problems with Ruby 1.9.* (#543805, #542927,
#590002) but all are supposed to be fixed.
Since it works fine on amd64, armel, i386, mips, mipsel, powerpc and s390, I
believe this is an architecture-specific problem. Ruby's test suite is known to
exercise threads in interesting ways.
--
| Lucas Nussbaum
| [email protected] http://www.lucas-nussbaum.net/ |
| jabber: [email protected] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
fixed 593139 1.9.3.194-1
fixed 593141 1.9.3.194-1
fixed 647296 1.9.3.194-1
thanks
Hi,
With the upload of version 1.9.3.194-1, ruby1.9.1 builds fine on amd64,
ia64 and kfreebsd-*. I am therefore closing the FTBFS bugs associated
with these architectures.
--
Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
