Your message dated Sat, 7 Jan 2012 21:32:23 +0000
with message-id <20120107213223.ga28...@einval.com>
and subject line Re: FTBFS on amd64: testsuite hangs
has caused the Debian Bug report #654777,
regarding FTBFS on amd64: testsuite hangs
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 ow...@bugs.debian.org
immediately.)
--
654777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby1.9.1
Version: 1.9.3.0-2
Severity: serious
Justification: fails to build from source
I'm trying to debug the armhf build failure (#652674) using valgrind,
which is showing up some nasty-looking warnings. In an attempt to
debug that faster, I'm trying to build ruby1.9.1 in an amd64 sid
chroot. That hangs in the testsuite:
...
TestPathname#test_parent_234 = 0.00 s = .
TestPathname#test_parent_235 = 0.00 s = .
TestPathname#test_parent_236 = 0.00 s = .
TestPathname#test_pathsub_506 = 0.00 s = .
TestPathname#test_pathsubext_509 = 0.00 s = .
TestPathname#test_pathsubext_510 = 0.00 s = .
TestPathname#test_pathsubext_511 =
^C
'make test-all' finished. checking number of failures and errors.
max number allowed: failures:30 errors:3
strace suggests things locked in a futex:
steve 29461 29459 68 17:12 pts/27 00:07:04 ./ruby1.9.1 --disable-gems
./test/runner.rb -v --ruby=./miniruby -I./lib -I. -I.ext/common
./tool/runruby.rb --extout=.ext -- --disable-gems
steve 31979 29461 0 17:17 pts/27 00:00:00
/home/steve/build/ruby/ruby1.9.1-1.9.3.0/ruby1.9.1
/home/steve/build/ruby/ruby1.9.1-1.9.3.0/test/drb/ut_eq.rb
druby://localhost:60641 ut_eq.rb
steve 32043 29461 0 17:17 pts/27 00:00:00
/home/steve/build/ruby/ruby1.9.1-1.9.3.0/ruby1.9.1
/home/steve/build/ruby/ruby1.9.1-1.9.3.0/test/drb/ut_array.rb
druby://localhost:60641 ut_array.rb
steve 32261 29461 0 17:17 pts/27 00:00:00
/home/steve/build/ruby/ruby1.9.1-1.9.3.0/ruby1.9.1
/home/steve/build/ruby/ruby1.9.1-1.9.3.0/test/drb/ut_array_drbssl.rb
druby://localhost:60641 ut_array_drbssl.rb
tack:~/build$ strace -p 31979
Process 31979 attached - interrupt to quit
futex(0x1da26a4, FUTEX_WAIT_PRIVATE, 1, NULL^C <unfinished ...>
Process 31979 detached
tack:~/build$ strace -p 32043
Process 32043 attached - interrupt to quit
futex(0x217b6a4, FUTEX_WAIT_PRIVATE, 1, NULL^C <unfinished ...>
Process 32043 detached
tack:~/build$ strace -p 32261
Process 32261 attached - interrupt to quit
futex(0x25596a4, FUTEX_WAIT_PRIVATE, 1, NULL^C <unfinished ...>
Process 32261 detached
tack:~/build$ ^C
Building in current sid, which means gcc-4.6 ver 4.6.2-11. I have
typescript output of the build available too - shout if it helps.
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Thu, Jan 05, 2012 at 05:35:47PM +0000, Steve McIntyre wrote:
>Package: ruby1.9.1
>Version: 1.9.3.0-2
>Severity: serious
>Justification: fails to build from source
>
>I'm trying to debug the armhf build failure (#652674) using valgrind,
>which is showing up some nasty-looking warnings. In an attempt to
>debug that faster, I'm trying to build ruby1.9.1 in an amd64 sid
>chroot. That hangs in the testsuite:
>
>...
>TestPathname#test_parent_234 = 0.00 s = .
>TestPathname#test_parent_235 = 0.00 s = .
>TestPathname#test_parent_236 = 0.00 s = .
>TestPathname#test_pathsub_506 = 0.00 s = .
>TestPathname#test_pathsubext_509 = 0.00 s = .
>TestPathname#test_pathsubext_510 = 0.00 s = .
>TestPathname#test_pathsubext_511 =
>^C
>'make test-all' finished. checking number of failures and errors.
>max number allowed: failures:30 errors:3
Hmmm. After an upgrade in my sid chroot, this does not show up any
more. Closing, and sorry for the noise. :-/
--
Steve McIntyre, Cambridge, UK. st...@einval.com
"C++ ate my sanity" -- Jon Rabone
--- End Message ---
