2016-10-04 15:22:58 UTC
In fact it's glibc, affected version: glibc-2.24.90-8I sent a heads-up about this to libc-alpha, here:
Something like the attached gnulib patch should work around the problem,
but I wonder whether we should bother given that it's bleeding-edge
glibc that will get fixed soon and that the failure is so unimportant.