Re: All (?) network tests failing

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sat, 4 Apr 2020 16:37:08 +0300
    From:        Andreas Gustafsson <gson%gson.org@localhost>
    Message-ID:  <24200.36228.881611.989244%guava.gson.org@localhost>

  | Does anyone have an idea why the tests didn't start failing
  | immediately when route.c 1.167 was committed, but only after the
  | seemingly unrelated openssl update?

Not an idea, but a possibility - the change to route.c (1.167) was
unimportant - it doesn't really matter (to the tests) if it does
anything useful or not - it is possible that it just happened that the
fd that the setsockopt() was being performed on was a socket (a suitable
socket) prior to the openssl update, but after that, the rump fd's
shifted around, and what the setsockopt() was operating upon was no
longer a socket.

No idea if that is really what happened or not, but something like that
is at least plausible (even though it would seem that the changes of the
sys call having worked by accident seem to be not very high).

kre