On Mon, Nov 27, 2006 at 12:13:06AM -0600, William Rowe wrote: > Joe Orton wrote: > > (The test_get_addr test was to check for a ->remote_addr_unknown > > handling bug alone, FWIW: PR 32737) > > Right - and it erroneously invokes connect against 0.0.0.0 no matter which > way I patch this. We need to determine that connect-to 0.0.0.0 is portable > behavior and emulate, correct the patch to connect to a non-ephemeral addr, > or revert the test.
I've changed it to use 127.0.0.1 on the trunk; does that help? > And we need to roll a tarball - this is getting silly. But I'm not rolling > with a borked test. The test has been in 1.2.x since September 2005 - did something change since then? Regards, joe
