Control: severity -1 important
Am 05.11.18 um 23:33 schrieb Bernhard Schmidt:
Hi,
>> this is where asterisk is actually segfaulting (not during the
>> testsuite, but when collecting the results). I haven't managed to pull
>> the backtrace from the autopkgtest worker yet.
Downgrading severity
Hi,
>
> this is where asterisk is actually segfaulting (not during the
> testsuite, but when collecting the results). I haven't managed to pull
> the backtrace from the autopkgtest worker yet.
Backtrace:
#0 ___fprintf_chk (fp=fp@entry=0x0, flag=flag@entry=1,
format=format@entry=0x555981d58a08
Hi,
> 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.
Okay, I tried to have a look at this and I have to admit I'm a bit confused.
First, I do see a failing unittest in MY autopkgtest qemu instance that
is not
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
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:
>
Source: asterisk
Version: 1:13.23.1~dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of asterisk the autopkgtest of asterisk fails in
testing when that autopkgtest is run with the binary packages of
6 matches
Mail list logo
