Excerpts from Danek Duvall's message of 2017-02-16 09:51:14 -0800: > Jun Wu wrote: > > > # HG changeset patch > > # User Jun Wu <qu...@fb.com> > > # Date 1487221422 28800 > > # Wed Feb 15 21:03:42 2017 -0800 > > # Node ID f2743873dfbd6adedcd3aa1777b651ce5bd6f6ed > > # Parent a70e11929c63cd9245812f3db8091a449cd1273e > > # Available At https://bitbucket.org/quark-zju/hg-draft > > # hg pull https://bitbucket.org/quark-zju/hg-draft -r > > f2743873dfbd > > runtests: export HGIPV6 to hint test scripts whether to use IPv6 > > > > Previously, run-tests.py only exports HGPORT, and scripts in tests do not > > know if IPv6 should be used. And that breaks scripts like dumbhttp.py which > > always uses IPv4. > > > > This patch makes run-tests.py export HGIPV6, which can help test scripts > > like dumbhttp.py and tinyproxy.py to decide whether to use IPv6 or not. > > So does this set of patches mean that if IPv6 is available on the test > machine, IPv4 won't be tested at all?
Yes, together with previous changes. Before the series, it's basically impossible to test on v6. With all the changes, it'll be easy to switch between v4 and v6 (by changing "useipv6" in run-tests.py). I think we can add a new command line flag to run-tests.py so people can choose whether they want to test v4 or v6. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
