Public bug reported:
socat 1.8.0.1-2 was recently stuck in proposed due to failures of flaky
build time tests. After tens of iterations in a local chroot, I failed
to reproduce the failures. In my PPA attempts, I saw failures on i386
and amd64 but quite intermittently (I had to run 10 builds to see the
first failure).
Here is a list of flaky tests for ./test.sh:
i386
----
test 512 UNIX_RECVFROM_SENDTO_BIND_TEMPNAME: Option unix-bind-tempname... FAILED
./socat -t 0.003000 -lp server
UNIX-RECVFROM:/tmp/buildd/17566/test512.sock0,fork PIPE &
2024/11/19 07:24:49 server[26106] E sendto(5, 0x6044a8d68000, 45, 0, AF=1
"/tmp/buildd/17566/test512.sock1.8TYGTC", 41): No such file or directory
2024/11/19 07:24:49 server[26087] W exiting on signal 15
./socat -t 0.003000 -lp tempname TCP4-LISTEN:12081,reuseaddr,fork
UNIX-SENDTO:/tmp/buildd/17566/test512.sock0,bind-tempname=/tmp/buildd/17566/test512.sock1.XXXXXX
&
2024/11/19 07:24:49 tempname[26089] W exiting on signal 15
./socat -t 0.003000 -lp client - TCP4-CONNECT:localhost:12081 &
./socat -t 0.003000 -lp client - TCP4-CONNECT:localhost:12081
test 516 ABSTRACT_RECVFROM_SENDTO_BIND_TEMPNAME: Option unix-bind-tempname...
FAILED
./socat -t 0.003000 -lp server
ABSTRACT-RECVFROM:/tmp/buildd/16728/test516.sock0,fork PIPE &
2024/11/19 07:29:30 server[25416] E sendto(5, 0x63bb2000, 45, 0, AF=1
"\0/tmp/buildd/16728/test516.sock1.8TYGTC\0", 42): Connection refused
2024/11/19 07:29:30 server[25398] W exiting on signal 15
./socat -t 0.003000 -lp tempname TCP4-LISTEN:12085,reuseaddr,fork
ABSTRACT-SENDTO:/tmp/buildd/16728/test516.sock0,bind-tempname=/tmp/buildd/16728/test516.sock1.XXXXXX
&
2024/11/19 07:29:30 tempname[25401] W exiting on signal 15
./socat -t 0.003000 -lp client - TCP4-CONNECT:localhost:12085 &
./socat -t 0.003000 -lp client - TCP4-CONNECT:localhost:12085
diff b:
1d0
---
amd64
-----
test 16 SYSTEMPIPESFDS: simple echo via system() of cat with pipes, non
stdio... FAILED:
./socat -t 0.003000 - SYSTEM:cat>&9 <&8,pipes,fdin=8,fdout=9
cat: write error: Broken pipe
2024/11/19 07:22:56 socat[17846] W exiting on signal 15
test 22 SYSTEMPIPESFDSFLUSH: call to od via system() with pipes, non stdio...
FAILED: diff:
./socat -t 0.003000 - SYSTEM:od -c>&9 <&8,pipes,fdin=8,fdout=9
od: write error: Broken pipe
2024/11/19 07:22:56 socat[17911] W exiting on signal 15
1,4d0
< 0000000 T u e N o v 1 9 0 7 : 2 2
< 0000020 : 5 6 U T C 2 0 2 4 4 0 6
< 0000040 5 \n
< 0000042
test 512 UNIX_RECVFROM_SENDTO_BIND_TEMPNAME: Option unix-bind-tempname... FAILED
./socat -t 0.003000 -lp server
UNIX-RECVFROM:/tmp/buildd/17566/test512.sock0,fork PIPE &
2024/11/19 07:24:49 server[26106] E sendto(5, 0x6044a8d68000, 45, 0, AF=1
"/tmp/buildd/17566/test512.sock1.8TYGTC", 41): No such file or directory
2024/11/19 07:24:49 server[26087] W exiting on signal 15
./socat -t 0.003000 -lp tempname TCP4-LISTEN:12081,reuseaddr,fork
UNIX-SENDTO:/tmp/buildd/17566/test512.sock0,bind-tempname=/tmp/buildd/17566/test512.sock1.XXXXXX
&
2024/11/19 07:24:49 tempname[26089] W exiting on signal 15
./socat -t 0.003000 -lp client - TCP4-CONNECT:localhost:12081 &
./socat -t 0.003000 -lp client - TCP4-CONNECT:localhost:12081
These look like infrastructure-related issues local to Launchpad. For
now, socat has migrated through a build retry. But we might consider
disabling some of these tests.
** Affects: socat (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089133
Title:
Flaky build-time tests while building on LP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/socat/+bug/2089133/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
