Automatic update for glibc-2.38.9000-4.fc40.
* Tue Aug 15 2023 Carlos O'Donell <carlos@redhat.com> - 2.38-4
- Collect dynamic loader diagnostics from the build system.
* Tue Aug 15 2023 Florian Weimer <fweimer@redhat.com> - 2.38-3
- Auto-sync with upstream branch master,
commit d6fe19facc61caffb25383d9c25eff86a0e115c8:
- configure: Add -Wall again to the default CFLAGS
- malloc: Remove bin scanning from memalign (bug 30723)
- resolv/nss_dns/dns-host: Get rid of alloca.
- x86_64: Add expm1 with FMA
- elf: Add new LoongArch reloc types (101 to 108) into elf.h
- x86: Fix incorrect scope of setting `shared_per_thread` [BZ# 30745]
- x86_64: Add log2 with FMA
- malloc: Enable merging of remainders in memalign (bug 30723)
- nscd: Do not rebuild getaddrinfo (bug 30709)
- x86_64: Sort fpu/multiarch/Makefile
- i686: Fix build with --disable-multiarch
- x86_64: Fix build with --disable-multiarch (BZ 30721)
- Add PTRACE_SET_SYSCALL_USER_DISPATCH_CONFIG etc. from Linux 6.4 to sys/ptrace.h
- Add PACKET_VNET_HDR_SZ from Linux 6.4 to netpacket/packet.h
- linux: statvfs: allocate spare for f_type
- x86: Fix for cache computation on AMD legacy cpus.
- powerpc longjmp: Fix build after chk hidden builtin fix
- LoongArch: Fix static PIE condition for toolchain bootstrapping.
- chk: Add and fix hidden builtin definitions for *_chk
- tst-realpath-toolong: return "unsupported" when PATH_MAX is undefined
- tst-*glob*: Do not check d_name size
- iconv: restore verbosity with unrecognized encoding names (bug 30694)
- configure: Remove --enable-all-warnings option
- Add IP_PROTOCOL from Linux 6.4 to bits/in.h
- Update kernel version to 6.4 in header constant tests
- PowerPC: Influence cpu/arch hwcap features via GLIBC_TUNABLES
- vfprintf-internal: Get rid of alloca.
- stdlib: Improve tst-realpath compatibility with source fortification
- Open master branch for glibc 2.39 development
Automatic update for glibc-2.38.9000-3.fc40.
Please login to add feedback.
This update was automatically created
This update has obsoleted glibc-2.38.9000-3.fc40, and has inherited its bugs and notes.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
The failures in the functional tests here seems like genuine ones indicating that we're leaking memory where we shouldn't be. @codonell
I'm not sure about the gating requirement for a
baseos-qe.koji-build.scratch-build.validationresult, though. I don't think Fedora CI would ever file such a result. It seems like maybe something that's bled in from RH internal CI?Ah, I understand about
baseos-qe.koji-build.scratch-build.validationnow (though the prefix is questionable...) - it's a test that does a scratch build of the kernel to check if this update breaks kernel build. It's supposed to be run on low level stuff like glibc and binutils.For some reason, it doesn't seem to be triggering on Rawhide updates - it is also missing for FEDORA-2023-573276711f . I've filed a Fedora CI issue on this: https://pagure.io/fedora-ci/general/issue/431
@adamwill Which failure specific worries you? I have trouble finding it in the results.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
@fweimer clicking "fedora-ci.koji-build.tier0.functional" in the results takes you to https://artifacts.dev.testing-farm.io/ec9547f2-b5cf-49ec-a5ca-01162e694495/ , which shows that "/tests/Regression/bz699724-Memory-leak-within-NSSLOW-Init-as-called-by" failed. The testout.log file gives pointers to more informative stuff under https://artifacts.dev.testing-farm.io/ec9547f2-b5cf-49ec-a5ca-01162e694495/work-civhb4gadw/plans/ci/execute/data/guest/default-0/tests/Regression/bz699724-Memory-leak-within-NSSLOW-Init-as-called-by-42/data/ , each file there seems to indicate some memory leakage is happening.
The bz699724 test is recently added and apparently still under development, so I'm not particularly worried about it. It still needs porting to Python 3.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been obsoleted by glibc-2.38.9000-5.fc40.