[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#923666: marked as done (cl-fad: flaky autopkgtest, segfaults most of the time)



Your message dated Mon, 04 Mar 2019 13:49:20 +0000
with message-id <E1h0ny4-00023V-5r@fasolo.debian.org>
and subject line Bug#923666: fixed in cl-fad 20180430-3
has caused the Debian Bug report #923666,
regarding cl-fad: flaky autopkgtest, segfaults most of the time
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
923666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923666
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: cl-fad
Version: 20180430-2
Severity: important
X-Debbugs-CC: debian-ci@lists.debian.org
User: debian-ci@lists.debian.org
Usertags: flaky

Dear maintainers,

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 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.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cl-fad/2054523/log.gz

autopkgtest [05:13:23]: test command3: clisp -norc
debian/tests/runtests.lisp
autopkgtest [05:13:23]: test command3: [-----------------------
0 errors, 0 warnings
WARNING: System definition file
         #P"/usr/share/common-lisp/source/cl-fad/cl-fad.asd" contains
         definition for system "cl-fad-test". Please only define
"cl-fad" and
         secondary systems with a name starting with "cl-fad/" (e.g.
         "cl-fad/test") in that file.
WARNING: Adding method
         #<STANDARD-METHOD (#<STANDARD-CLASS TEST-OP> (EQL #<SYSTEM
         "bordeaux-threads">))> to an already called generic function
         #<STANDARD-GENERIC-FUNCTION PERFORM>
;; Compiling file /usr/share/common-lisp/source/alexandria/package.lisp ...
;; Wrote file
/tmp/autopkgtest-lxc.0pahl99q/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/alexandria/package-tmpB5X7U7YO.fas
;; Compiling file
/usr/share/common-lisp/source/alexandria/definitions.lisp ...
;; Wrote file
/tmp/autopkgtest-lxc.0pahl99q/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/alexandria/definitions-tmpCTOW975M.fas
*** - handle_fault error2 ! address = 0x1fffffe18bb0 not in
[0x80000c0000,0x80003a2750) !
SIGSEGV cannot be cured. Fault address = 0x1fffffe18bb0.
GC count: 39
Space collected by GC: 37780248
Run time: 0 632000
Real time: 1 44101
GC time: 0 132000
Permanently allocated: 180024 bytes.
Currently in use: 5481232 bytes.
Free space: 1106064 bytes.
bash: line 1:   945 Segmentation fault      bash -ec 'clisp -norc
debian/tests/runtests.lisp' 2> >(tee -a
/tmp/autopkgtest-lxc.0pahl99q/downtmp/command3-stderr >&2) > >(tee -a
/tmp/autopkgtest-lxc.0pahl99q/downtmp/command3-stdout)
autopkgtest [05:13:24]: test command3: -----------------------]

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: cl-fad
Source-Version: 20180430-3

We believe that the bug you reported is fixed in the latest version of
cl-fad, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 923666@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot <sebastien@debian.org> (supplier of updated cl-fad package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 04 Mar 2019 14:24:52 +0100
Source: cl-fad
Architecture: source
Version: 20180430-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team <debian-common-lisp@lists.debian.org>
Changed-By: Sébastien Villemot <sebastien@debian.org>
Closes: 923666
Changes:
 cl-fad (20180430-3) unstable; urgency=medium
 .
   * Mark the autopkgtest for clisp as flaky. It often segfaults.
     (Closes: #923666)
Checksums-Sha1:
 24d502d1fdcab5dc9760b3957a082d3566d99c26 1976 cl-fad_20180430-3.dsc
 500fbb2f98980b9a9c933370eea207da5d08791b 2988 cl-fad_20180430-3.debian.tar.xz
 496eda74643e695e7202da1a6537f4c614d28ac6 5254 cl-fad_20180430-3_amd64.buildinfo
Checksums-Sha256:
 ef2eab0b0b315734bdb77fc9d6dd940f077352315dd2fd68a10cfd8318d19458 1976 cl-fad_20180430-3.dsc
 c1532d99416f8cdc62dd1e3088dafb8590bb25005eb5d1952228c00f4304ce29 2988 cl-fad_20180430-3.debian.tar.xz
 a54941430e2f3b985e3a20f8949ca16cec1ea90de3c9565e84c6b467ebcc6b0e 5254 cl-fad_20180430-3_amd64.buildinfo
Files:
 dc8f28164a797f64cbb820e085b58d9b 1976 lisp optional cl-fad_20180430-3.dsc
 8561a4959996af32c6219db60381800c 2988 lisp optional cl-fad_20180430-3.debian.tar.xz
 c2946ba41fa06fd8504871a05ba6ba24 5254 lisp optional cl-fad_20180430-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlx9KBAACgkQLOzpNQ7O
vkpuAA/+Lx4ZhoKXKI3Zu5aYRYscKTx78+5HipxRSPvxE4Nk5JtK4T3EM4aAmxiK
/laeeJ9ljFZ+YdvMlU+SdLL6DqGq/Jv/Kfg9Om/li3v4+i4MQxJ+9eAHtd3onNcQ
m9iLZkAM6uAjvuZTIm1izq9Z3k7oWSbleb3WDO2GOfmeIRGdSDyGkOQ5grYH4tiO
sfwkCuIb5hD0IgjKeAVqpelHAfSudAPb7XYkHbtxWL6pPDkV7bPwHwyKfozkhcfR
qy+oOUEXEX8p/7tYu8d5/rs+JqXXNAN1kykIEcvBHtpb1MN/OahhmW9SjuQ1dfNO
T0Ieb2p0PWrBkdGiy/DOSOBkvJiasFqLXenZ+5YaTDe3q7aToSqYh3TJ2w9Q61XI
uZV9B7IJNQMaO13+5xMdwsHTakOIU6/zMw7hfZnb4VIo/4Ia694nMNytM4rYZUjO
hVqIkKZQV7ReUGzCsGuBU6PCQoxDQ+yzWrjQffAlxTZamtx7XO5FLPOM9ZIBlufy
O+Iy0ZepYuFsf9j9cR8+/mOc3/yACIseQiP9PUoTcmjvmuWozr2yN8oOHXsFw+VR
+zxhDwSh6joGnIJV61UneQkyUxH7wjZUski6HUclGoXHu2XOdfhNf71xDgMm3h0A
Y9VJakACy/XxzUyTZt7QuCd1Ni7fFRjK2GzlUDo9mMsRB/qZzqA=
=kf3B
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: