On 2020-12-07, Andreas Metzler wrote:
> On 2020-12-07 Ludovic Courtès <l...@gnu.org> wrote:
>> Vagrant Cascadian <vagr...@debian.org> skribis:
> [...]
>> > I was never able to reproduce the failure locally on multiple occasions,
>> > although once triggered a rebuild on the buildd machines that failed in
>> > the same way.
>
>> Same here and I don’t think we got a report upstream in GnuTLS either.
>
> See below for a reproducer:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969672#48
> | how to reproduce this on amd64 in the other
> | bugreport:
> | 
> | (sid)ametzler@argenau:/$ rm -rf /tmp/GNUTLS/  /dev/shm/GNUTLS
> | (sid)ametzler@argenau:/$ mkdir /tmp/GNUTLS/  /dev/shm/GNUTLS
> | (sid)ametzler@argenau:/$ cd /dev/shm/GNUTLS
> | (sid)ametzler@argenau:/dev/shm/GNUTLS$ apt source gnutls28 ; ln -s 
> /dev/shm/GNUTLS/gnutls28-3.6.15 /tmp/GNUTLS/ ; cd /tmp/GNUTLS/gnutls28-3.6.15
> | (sid)ametzler@argenau:/tmp/GNUTLS/gnutls28-3.6.15$ dpkg-buildpackage -uc 
> -us -j1 -B

Ok, I can now reproduce it, and uncommented the debugging code in
guile/tests/reauth.scm; log from a hung test attached.


live well,
  vagrant

Attachment: reauth.scm.log.gz
Description: application/gzip

Attachment: signature.asc
Description: PGP signature

Reply via email to