Hi!

This patch disables 27 additional tests for the Hurd, and enabled me to
build (a copy of) python-minimal natively

--8<---------------cut here---------------start------------->8---
/gnu/store/9xm1idqyvyyz6xcqaa20aw2p8ap9zxcj-python-hurd-minimal-3.8.2
--8<---------------cut here---------------end--------------->8---

That sounds bad, but Debian disables ~15 tests by default (varies per
platform), where we only disable test_socket, and 17 additional for the
Hurd:

    https://salsa.debian.org/cpython-team/python3/-/raw/python3.8/debian/rules

and our exclude sets have some overlap, but also some "underlap"...

It's tempting to do

--8<---------------cut here---------------start------------->8---
#:tests? ,(not (hurd-target?))
--8<---------------cut here---------------end--------------->8---

just like https://bugs.gnu.org/43857 suggests:

    "rather not fiddle too much with test suites until we have defined
     what’s available in the default build environment."

on the other hand, now some 350 tests run and pass.  (It would be nice
if Python had a less fragile test suite, or if packages (the GNU
standard?) defined a "smoke test" we could run.)

Then there is also this 2013 bug report in Debian

    https://bugs.debian.org/708652
    "hurd has several tests disabled because they hang the testsuite, at
     least on the buildds. These should be investigated..."

and we/they probably will, when someone finds the time.

One last thing: pushing this patch rebuilds world for the Hurd; probably
not the best timing to push today?  Ideas?

Greetings,
Janneke