Dear Paul, Le dimanche 03 mars 2019 à 15:02 +0100, Paul Gevers a écrit : > Source: cl-fad > Version: 20180430-2 > Severity: important > X-Debbugs-CC: debian-ci@lists.debian.org > User: debian-ci@lists.debian.org > Usertags: flaky > With a recent upload of sbcl the autopkgtest of cl-fad fails in testing > when that autopkgtest is run with the binary packages of sbcl from > unstable. I looked at the history of the results of autopkgtest for your > package and discovered that if fails most of the time with the same > segfault, I copied some of the output at the bottom of this report. I think this has nothing to do with sbcl. The failure happens in the autopkgtest run with clisp, so the problem is rather in clisp. > I am not sure if this is showing a severe issue that already exist or is > "just" an issue with your autopkgtest. In the latter case, please fix > your autopkgtest or mark this particular test as flaky. I think I'll mark it as flaky, since clisp is a second-tier and under- maintained Common Lisp implementation. Do you think it is worth making this change now, given that I'll have to ask for an unblock? Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part