#5059 Failure of -myaddr localhost

obsolete: 8.6b2
closed-works-for-me
Reinhard Max
3
2012-06-22
2012-06-22
Don Porter
No

On my MacBook Pro running OSX 10.6.8, I get this failure:

% socket -server foo -myaddr localhost 0
couldn't open socket: host is unreachable (nodename nor servname provided, or not known)

Several tests in http11.test, socket.test and zlib.test expect this to work, so the test suite
is not what it needs to be for this platform.

Discussion

  • Don Porter
    Don Porter
    2012-06-22

    Bisecting reveals this failure started with checkin

    3f8b48b6b6761db092f2a7c0193fc4b71349640f 2010-09-28 15:13:54 UTC

     
  • Don Porter
    Don Porter
    2012-06-22

    • assigned_to: dkf --> rmax
     
  • Don Porter
    Don Porter
    2012-06-22

    And testing again the next day the problem has vanished, so there's
    at least an element of transient system failure contributing.

     
  • Don Porter
    Don Porter
    2012-06-22

    • priority: 8 --> 3
     
  • Reinhard Max
    Reinhard Max
    2012-06-22

    As discussed on the chat, it looks like that machine temporarily loses its ability to resolve localhost.
    Nothing that Tcl can do anything about.

     
  • Reinhard Max
    Reinhard Max
    2012-06-22

    • status: open --> closed-works-for-me
     
  • Don Porter
    Don Porter
    2012-06-22

    Please note that Tcl does play some role in this failure as well.
    Even during that extended time period where my system wasn't
    able to resolve "-myaddr localhost" using the trunk of Tcl, it was able
    to do so using builds of Tcl prior to checkin 3f8b48b6.

    So Tcl has evolved in a way that makes it vulnerable to this mystery
    system trouble where it did not used to be.