Control: severity -1 serious Am 26.09.18 um 21:51 schrieb Bernhard Schmidt: > Am 26.09.18 um 20:48 schrieb Paul Gevers: > > Hi Paul, > >> With a recent upload of asterisk the autopkgtest of asterisk fails in >> testing when that autopkgtest is run with the binary packages of >> asterisk from unstable. It passes when run with only packages from >> testing. In tabular form: >> pass fail >> asterisk from testing 1:13.23.1~dfsg-1 >> all others from testing from testing >> >> I copied some of the output at the bottom of this report. It seems that >> the test passes in the sense that the exit code is still 0 (is that >> correct?). However, there is output on stderr which is treated as an >> error. Ideally the output to stderr should be fixed, but otherwise >> adding a allow-stderr restriction to the test definition will make sure >> this output is ignored. > > We're aware of this, thanks. > > The autopkgtest shows a real regression. The testsuite itself appears > fine, but when getting the results and stopping asterisk in the end we get > >> Unable to connect to remote asterisk (does >> /var/run/asterisk/asterisk.ctl exist?) >> Unable to connect to remote asterisk (does >> /var/run/asterisk/asterisk.ctl exist?) > > Which means asterisk already quit.
So, asterisk is really segfaulting inside autopkgtest :-O Sep 26 20:21:50 debian asterisk[2658]: radcli: rc_read_config: rc_read_config: can't open /etc/radiusclient-ng/radiusclient.conf: No such file or directory Sep 26 20:21:50 debian asterisk[2658]: radcli: rc_read_config: rc_read_config: can't open /etc/radiusclient-ng/radiusclient.conf: No such file or directory [...] Sep 26 20:24:57 debian kernel: asterisk[3124]: segfault at 0 ip 00007f88fff90dab sp 00007f88c81a8080 error 4 in libc-2.27.so[7f88ffeac000+146000] I don't know how much time I'll have to check on this in the next days. Raising severity to block testing migration for now. Bernhard
