Hello aurel32 et al.

When I try to build glibc on AWS instances with 1 CPU, the test below fails
approximately 12% of the time (currently 7 out of 58 tries).

This is unexpected because building glibc has always been extremely
reliable (I did not remember it failing to build randomly, ever).

I've put several build logs here for reference:

https://people.debian.org/~sanvila/build-logs/202610/

(To reproduce, try GRUB_CMDLINE_LINUX="nr_cpus=1", if that does not
work I can offer a VM to test, as always).

Thanks.
--------------------------------------------------------------------------------
[...]
Flavour cross-compiled, tests have been skipped.
touch /<<PKGBUILDDIR>>/stamp-dir/check_x32
CHECK SUMMARY
check for check_i386 passed
check for check_libc failed
  FAIL: nptl/tst-basic3
make: *** [debian/rules.d/build.mk:210: build-arch-post-check] Error 1
rm /<<PKGBUILDDIR>>/stamp-dir/mkbuilddir_libc /<<PKGBUILDDIR>>/stamp-dir/configure_i386 /<<PKGBUILDDIR>>/stamp-dir/configure_libc /<<PKGBUILDDIR>>/stamp-dir/configure_x32 /<<PKGBUILDDIR>>/stamp-dir/mkbuilddir_x32 /<<PKGBUILDDIR>>/stamp-dir/mkbuilddir_i386
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------