Bug #6356
closedarm linux build test suite fails on test/socket
Description
consistent unix address errors in 3 places, plus 1 failure in socket test suite
kind regards
Steve
[root@techbase /mnt/nand-user/ruby-1.9.2-p136]# /mnt/nand-user/ruby/bin/ruby test/socket/*
Loaded suite test/socket/test_addrinfo
Started
.F..........E.......E...E...........
Finished in 0.299011 seconds.
-
Failure:
test_addrinfo_inspect_sockaddr_unix(TestSocketAddrinfo) [test/socket/test_addrinfo.rb:583]:
<"/testdir/test_addrinfo_inspect_sockaddr_unix"> expected but was
<"/testdir/test_addrinfo_inspect_sockaddr_unix(sockaddr 2 bytes too long)">. -
Error:
test_addrinfo_unix_path(TestSocketAddrinfo):
SocketError: too long AF_UNIX address
test/socket/test_addrinfo.rb:578:inunix_path' test/socket/test_addrinfo.rb:578:in
test_addrinfo_unix_path' -
Error:
test_family_addrinfo(TestSocketAddrinfo):
SocketError: too long AF_UNIX address
test/socket/test_addrinfo.rb:322:inunix_path' test/socket/test_addrinfo.rb:322:in
test_family_addrinfo' -
Error:
test_marshal_unix(TestSocketAddrinfo):
SocketError: too long AF_UNIX address
test/socket/test_addrinfo.rb:607:inunix_path' test/socket/test_addrinfo.rb:607:in
test_marshal_unix'
36 tests, 130 assertions, 1 failures, 3 errors, 0 skips
Test run options: --seed 48470
[root@techbase /mnt/nand-user/ruby-1.9.2-p136]#
Updated by mame (Yusuke Endoh) about 12 years ago
- Status changed from Open to Feedback
At first, please try Ruby trunk.
If the problem still occurs, could you please create a patch yourself?
There is no arm maintainer unfortunately.
If your patch looks benign for other platforms, we may import it.
Thanks,
--
Yusuke Endoh mame@tsg.ne.jp
Updated by akr (Akira Tanaka) about 12 years ago
2012/4/25 stevegoobermanhill (stephen gooberman-hill)
stevegoobermanhill@gmail.com:
Issue #6356 has been reported by stevegoobermanhill (stephen gooberman-hill).
ruby -v: ruby 1.9.2p136 (2010-12-25 revision 30365) [arm-linux]
consistent unix address errors in 3 places, plus 1 failure in socket test suite
I couldn't reproduce the problem. (I don't have arm-linux.)
However I tried to review unix socket path code and make it more consistent.
Try ruby trunk.¶
Tanaka Akira
Updated by mame (Yusuke Endoh) over 11 years ago
- Status changed from Feedback to Rejected
No feedback, we cannot grasp the current situation. Closing.
--
Yusuke Endoh mame@tsg.ne.jp