Your message dated Sat, 01 May 2021 22:03:47 +0000
with message-id <e1lcxif-0008cn...@fasolo.debian.org>
and subject line Bug#985617: fixed in glibc 2.31-12
has caused the Debian Bug report #985617,
regarding glibc: flaky autopkgtest on most architectures
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 ow...@bugs.debian.org
immediately.)


-- 
985617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.31-9
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] and I noticed it fails regularly
on lately. Unfortunately, the log of glibc is so long that it gets
truncated on the ci.d.n infrastructure, so I can't copy any useful log.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Please get in touch if you need a full log, I can try to generate one.

Paul

https://ci.debian.net/packages/g/glibc/testing/amd64/
https://ci.debian.net/packages/g/glibc/testing/arm64/
https://ci.debian.net/packages/g/glibc/testing/armhf/
https://ci.debian.net/packages/g/glibc/testing/i386/


Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-12
Done: Aurelien Jarno <aure...@debian.org>

We believe that the bug you reported is fixed in the latest version of
glibc, 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 985...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aure...@debian.org> (supplier of updated glibc 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Sat, 01 May 2021 22:56:06 +0200
Source: glibc
Architecture: source
Version: 2.31-12
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Aurelien Jarno <aure...@debian.org>
Closes: 973278 985617 986450
Changes:
 glibc (2.31-12) unstable; urgency=medium
 .
   * debian/po/de.po: fix encoding declaration.  Closes: #986450.
   * debian/patches/git-updates.diff: update from upstream stable branch:
     - On s390x, check for vector support in memmove ifunc-selector in
       addition to Miscellaneous-Instruction-Extensions.
   * debian/patches/any/local-rtlddir-cross.diff: drop patch, letting upstream
     makefiles to install the dynamic linker symlink directly in the right
     location. This fixes the temporary installation done by upstream makefiles
     to run some tests in a container.  Closes: #973278, #985617.
   * debian/rules.d/build.mk: do not create the dynamic linker manually.
   * debian/sysdeps/*.mk: do not create the dynamic linker manually for
     bi/tri-arch packages.
   * debian/rules.d/build.mk: create the soname symlink for ld-2.xx.so, to
     avoid its creation later by ldconfig.
   * debian/debhelper.in/libc.install, debhelper.in/libc-alt.install,
     debhelper.in/libc-udeb.install, debhelper.in/libc-udeb.install.hurd-i386:
     adjust given that the dynamic linker symlink is now already at the correct
     location.
   * debian/patches/git-updates.diff: update from upstream stable branch:
     - Fix GLIBC_TUNABLES parsing for AT_SECURE binaries.
   * debian/rules.d/build.mk: escape EOL so that $configure_build is correctly
     passed to the configure script.
Checksums-Sha1:
 5623eddc5e35ff0cff5d64eed3681c7e3bb1ddbb 8315 glibc_2.31-12.dsc
 530552fdebb574b285c3d8068de390e65e267d17 911388 glibc_2.31-12.debian.tar.xz
 557c295057a7c9b1fba16adc2e0de9fe2d589c9d 8935 glibc_2.31-12_source.buildinfo
Checksums-Sha256:
 2c749d8b218f0802edcb6c9850db968815711f627e66f1c925cece12d652f79a 8315 
glibc_2.31-12.dsc
 8377ea637b5c0aaa3afc26805ff39aadc1e58ea3cfcd5ced4a2823f16178c7c8 911388 
glibc_2.31-12.debian.tar.xz
 97fe182a37c91afe601269738d13694d6b35aa71ac814afb4d521d0e22e7a310 8935 
glibc_2.31-12_source.buildinfo
Files:
 9c84c64a3a9e254a2773ffde1a6cf636 8315 libs required glibc_2.31-12.dsc
 db986d5c13d2629fd336763a54471ae7 911388 libs required 
glibc_2.31-12.debian.tar.xz
 65ae57e90840cf23152c170defd6d120 8935 libs required 
glibc_2.31-12_source.buildinfo

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

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmCNwmcACgkQE4jA+Jno
M2tIPQ/7BDl1r4XfbPUyKm540BcrEgYuhnLmyrhLxUYHO9zWU+zbYktPASMQ+hVy
2+SzMI3XXDBG5q4KMeHizkWQA7hYAewXg3Cy4BIeJpfYAl0yLmdBulzsvFw0wHMV
Z2pkGrz4G6+sE3Tbk1clG47GD4ijF0nYoXKQJOttIPLxVy7/GKlTB8IK8LoEaihV
LXlAeji3CbnEPb2AiMdDL8CjEhibxQW5wlGIR4iUFjAI7MCa+ui3jnn6bLH15mcf
Efcgf2vPZANnqsN3qAXel5IDIdA7FWmkXOV1iAwG8nVdo3/GEAYZYozSZJN3P54k
k6eSvkzMsl4RpbwVbfummkNaqf7BAwbZjIocjRT5ESGY1SDjqIR2rnqfXro5G9LA
swGwYWPeUtbmqNhEEaxoG/5W+MRf1uXM+rkBZkJroZyydsMrJkvPsm51LxuHVUNM
w7RyVIH5mDp+zIhzEdTcPQp1ZTpbQRXDDjRtS28w1dGSzz1qzwFtcyfk/kOwHtue
RKgfI7ByRiph1YJgKVBDWtrrXZV02KHWEP4cEvqEZnNzmTscc3Txj/pE+B3N/Tp3
H2XkxhCfyJgVJxcUHHYdZPO3ejehR4PJD8gLNhkxcFZbNwgFGfeVnazX5fHyjChH
M7+RZZCpUNUOlLG8VmE5o5U8I/AHFgMAztbqiiIwwPmJ3/pSpfw=
=H1HQ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to