Hello, Vagrant Cascadian <vagr...@debian.org> skribis:
> On 2020-07-04, Vagrant Cascadian wrote: >> The attached patch updates guile-gnutls to use guile 3.0, which is the >> current version of guile, available in unstable and bullseye. It would >> be ideal if the switch happened before bullseye was released. > > This was reverted in the recent upload of 3.7.0-1. Well, mostly > reverted; the package now depends on guile-3.0 and guile-libs-2.2, but > does not ship any guile-3.0 files. > > I presume this was due to build failures due to the test suite hanging > on arm64 on previous versions: > > > https://buildd.debian.org/status/fetch.php?pkg=gnutls28&arch=arm64&ver=3.6.15-5&stamp=1605401160&raw=0 > > By process of elimination(e.g. all other tests claim to have PASSED), > the hanging test for 3.6.15-5 was: > > guile/tests/reauth.scm > > 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. Would it be an option for you to have a ‘guile3-gnutls’ package so ‘guix’ can depend on it? > For more possibly relevent and related background: > > https://bugs.debian.org/969672 gnutls28: please upgrade to guile-3.0 soon, > if feasible > https://bugs.debian.org/966714 guile-gnutls: FTBFS against guile 3.0.4-1+b1 If you can reproduce the hang, could you attach gdb to the two processes that run tests/reauth.scm (it forks)? On the ‘gnutls_3_6_X’ branch, I can run the following loop for a while without experiencing the issue (on x86_64-linux-gnu): while make check TESTS=tests/reauth.scm ; do : ; done Thanks in advance, Ludo’.
