killall fails test suite on musl
Not sure how long this has actually been failing, as the addition to the test suite is the first bad commit per git bisect
.
258ee9166e585f87005d3a9686938a4fa26669f9 is the first bad commit
commit 258ee9166e585f87005d3a9686938a4fa26669f9
Author: Craig Small <csmall@enc.com.au>
Date: Tue Sep 18 21:17:00 2018 +1000
killall: Another go at option parsing
This now seems to be working. There are some evil hacks, especially for
the -ve option combination but it seems that we have a winner.
Added a bunch more option parsing tests which picked up -ILL passed but
-VTALRM did not. Not sure why, but length seems my guess
References:
psmisc/psmisc#13
psmisc/psmisc#12
:100644 100644 16f3c19d4f9c616ce29cfa30f038b854e7f1fb02 7fd2abdc34117776dbdff0df547c557ac6a2bfd9 M ChangeLog
:040000 040000 cb36d41b768cba4a4cee66aee666a81a741882cc 4b6336260b1c1609eb420086ef3c51736cb0958f M src
:040000 040000 fa8973433e4cf2242996dad218bf57833cc9f903 fd1aa21799bba193c4177d8e79f34affeb1c2b27 M testsuite
Test run by awilcox on Fri Mar 8 05:24:31 2019
Native configuration is powerpc64-foxkit-linux-musl
=== killall tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./killall.test/killall.exp ...
FAIL: killall using signal HUP
FAIL: killall using signal SIGHUP
FAIL: killall using signal SIGINT
FAIL: killall using signal QUIT
FAIL: killall using signal SIGQUIT
FAIL: killall using signal SIGILL
FAIL: killall using signal TRAP
FAIL: killall using signal SIGTRAP
FAIL: killall using signal ABRT
FAIL: killall using signal SIGABRT
FAIL: killall using signal BUS
FAIL: killall using signal SIGBUS
FAIL: killall using signal FPE
FAIL: killall using signal SIGFPE
FAIL: killall using signal KILL
FAIL: killall using signal SIGKILL
FAIL: killall using signal USR1
FAIL: killall using signal SIGUSR1
FAIL: killall using signal SEGV
FAIL: killall using signal SIGSEGV
FAIL: killall using signal USR2
FAIL: killall using signal SIGUSR2
FAIL: killall using signal PIPE
FAIL: killall using signal SIGPIPE
FAIL: killall using signal ALRM
FAIL: killall using signal SIGALRM
FAIL: killall using signal TERM
FAIL: killall using signal SIGTERM
FAIL: killall using signal STKFLT
FAIL: killall using signal SIGSTKFLT
FAIL: killall using signal CHLD
FAIL: killall using signal SIGCHLD
FAIL: killall using signal CONT
FAIL: killall using signal SIGCONT
FAIL: killall using signal STOP
FAIL: killall using signal SIGSTOP
FAIL: killall using signal TSTP
FAIL: killall using signal SIGTSTP
FAIL: killall using signal TTIN
FAIL: killall using signal SIGTTIN
FAIL: killall using signal TTOU
FAIL: killall using signal SIGTTOU
FAIL: killall using signal URG
FAIL: killall using signal SIGURG
FAIL: killall using signal XCPU
FAIL: killall using signal SIGXCPU
FAIL: killall using signal XFSZ
FAIL: killall using signal SIGXFSZ
FAIL: killall using signal SIGVTALRM
FAIL: killall using signal PROF
FAIL: killall using signal SIGPROF
FAIL: killall using signal WINCH
FAIL: killall using signal SIGWINCH
FAIL: killall using signal SIGIO
FAIL: killall using signal PWR
FAIL: killall using signal SIGPWR
FAIL: killall using signal SYS
FAIL: killall using signal SIGSYS
=== killall Summary ===
# of expected passes 8
# of unexpected failures 58
If I had to venture a guess, I'd think that this was related to the getopt_long_only to getopt_long change.