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 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.
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-protectio n2) 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: ------- ------- ------- - backtrace5
-------
FAIL: debug/tst-
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: ------- ------- ------- ------- ------- ------- ------- ------- ------- --- copy_file_ range
-------
FAIL: io/tst-
Failures from an eoan VM building glibc_2.29-0ubuntu3 locally: ------- ------- ------- ------- ------- ------- ------- ------ condattr- printers cond-printers mutexattr- printers mutex-printers rwlockattr- printers rwlock- printers
-------
FAIL: nptl/test-
FAIL: nptl/test-
FAIL: nptl/test-
FAIL: nptl/test-
FAIL: nptl/test-
FAIL: nptl/test-
I am currently trying to see if perhaps a different host kernel behaves differently for the schroot build case.