I am a bit stumped on this one - glibc_2.29-0ubuntu3 built fine in my PPA (https://launchpad.net/~alexmurray/+archive/ubuntu/gcc-stack-clash- protection2) but FTBFS on amd64/i386 for eoan-proposed - but I cannot reproduce the same failure locally either in an schroot or in an eoan VM - however, it does still FTBFS in both cases locally BUT with different tests failing (and different than the eoan-proposed failures):
Failures from eoan-proposed: ----------------------------- FAIL: debug/tst-backtrace5 FAIL: nptl/tst-cancel24 FAIL: nptl/tst-cancelx16 FAIL: nptl/tst-cancelx18 FAIL: nptl/tst-cancelx20 FAIL: nptl/tst-cancelx21 FAIL: nptl/tst-cancelx4 FAIL: nptl/tst-cancelx5 FAIL: nptl/tst-oncex3 FAIL: nptl/tst-oncex4 Failures from an eoan schroot running on a bionic (with hwe kernel) host: ------------------------------------------------------------------------- FAIL: io/tst-copy_file_range Failures from an eoan VM building glibc_2.29-0ubuntu3 locally: -------------------------------------------------------------- FAIL: nptl/test-condattr-printers FAIL: nptl/test-cond-printers FAIL: nptl/test-mutexattr-printers FAIL: nptl/test-mutex-printers FAIL: nptl/test-rwlockattr-printers FAIL: nptl/test-rwlock-printers I am currently trying to see if perhaps a different host kernel behaves differently for the schroot build case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833067 Title: FTBFS on amd64 / i386 when compiled with new hardening defaults in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1833067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
