Excerpts from Augie Fackler's message of 2017-02-15 21:32:38 -0500: > On Wed, Feb 15, 2017 at 06:26:11PM -0800, Jun Wu wrote: > > Excerpts from Augie Fackler's message of 2017-02-15 21:23:37 -0500: > > > I'm not overjoyed at the static default. Is there a reason to use the > > > static default instead of checking HGPORT, so that multiple users on a > > > single box (such as the big compile farm machine several of us favor) > > > can run the tests without risk of stomping each other? > > > > That's just a random default which must > 1024. If multiple users run this > > in parallel - it'd be fine - one of them will get the error EADDRINUSE, and > > that's considered "IPv6 is available". > > Oh, I misunderstood. This function is *only* for checking that IPv6 is > available, not also for checking if a specific port is available with > IPv6. Is that (revised) understanding correct on my part?
Correct. run-tests.py will first decide whether to use IPv6 or not globally by calling this function. If IPv6 is available, then all port checks will be IPv6-only. Otherwise, they will be IPv4-only. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel