Hello,
util-linux is failing to build for both hurd architectures[1] which I just
noticed while looking for the new hwclock patches-
Both seem to fail when running the logger/errors tests:
--- >8 --- >8 --- >8 --- >8 ---
== hurd-i386 ==
script: /build/reproducible-path/util-linux-2.41/tests/ts/logger/errors
commands: /build/reproducible-path/util-linux-2.41/
helpers: /build/reproducible-path/util-linux-2.41/
sub dir: /build/reproducible-path/util-linux-2.41/tests/ts/logger
top dir: /build/reproducible-path/util-linux-2.41/tests
self: /build/reproducible-path/util-linux-2.41/tests/ts/logger
test name: errors
test desc: errors
component: logger
namespace: logger/errors
verbose: yes
output:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors
error log:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors.err
exit code:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors.exit_code
valgrind:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors.vgdump
expected:
/build/reproducible-path/util-linux-2.41/tests/expected/logger/errors{.err}
mountpoint:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors-mnt
logger: errors ...
E: Build killed with signal TERM after 180 minutes of inactivity
== hurd-amd64 ==
script: /build/reproducible-path/util-linux-2.41/tests/ts/logger/errors
commands: /build/reproducible-path/util-linux-2.41/
helpers: /build/reproducible-path/util-linux-2.41/
sub dir: /build/reproducible-path/util-linux-2.41/tests/ts/logger
top dir: /build/reproducible-path/util-linux-2.41/tests
self: /build/reproducible-path/util-linux-2.41/tests/ts/logger
test name: errors
test desc: errors
component: logger
namespace: logger/errors
verbose: yes
output:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors
error log:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors.err
exit code:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors.exit_code
valgrind:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors.vgdump
expected:
/build/reproducible-path/util-linux-2.41/tests/expected/logger/errors{.err}
mountpoint:
/build/reproducible-path/util-linux-2.41/tests/output/logger/errors-mnt
logger: errors ...
E: Build killed with signal TERM after 180 minutes of inactivity
E: Build killed with signal KILL after 360 minutes of inactivity
--- >8 --- >8 --- >8 --- >8 ---
It turns out that the timeout comes from a pair of `socat` instances that fail
to communicate
(I beleive).[2]
On Hurd, the connecting instance hangs:
# Listening side
demo@debian:~/dev/tests/util-linux/socat$ socat \
-u UNIX-LISTEN:./socket,fork,max-children=1,backlog=128 \
STDOUT
# Connecting side
demo@debian:~/dev/tests/util-linux/socat$ socat \
-u /dev/null \
UNIX-CONNECT:./socket,retry=30,interval=0.1
(hangs)
On Linux, on the other hand, the connecting side return with 0 exit code:
# Listening side
diego@openwrt-builder:~/dev/tests/util-linux/socat$ socat \
-u UNIX-LISTEN:./socket,fork,max-children=1,backlog=128 \
STDOUT
# Connecting side
diego@openwrt-builder:~/dev/tests/util-linux/socat$ socat \
-u /dev/null \
UNIX-CONNECT:./socket,retry=30,interval=0.1
diego@openwrt-builder:~/dev/tests/util-linux/socat$ echo $?
0
I'll try to attach gdb to the connecting socat to see if I can find
where it's hanging. But if something rings a bell (like /dev/null usage
maybe) I'm all ears :)
[1] https://buildd.debian.org/status/package.php?p=util-linux
[2]
https://github.com/util-linux/util-linux/blob/master/tests/functions.sh#L1138
Thanks,
Diego
