Mercurial > hg
view tests/test-check-py3-commands.t @ 30851:7bfe02b57695 stable
tests: also allow "Protocol not supported" in test-http-proxy error
I've seen this in a (misconfigured) FreeBSD jail which has ::1 as an
entry for localhost, but IPv6 support is disabled in the jail. It took
me months to figure out what was going on (and I only figured it out
when tinyproxy.py got confused by similar IPv4-level misconfiguration
of the localhost domain in /etc/hosts.)
I don't feel strongly about this patch: on the one hand, it's papering
over a host-level misconfiguration, but on the other it avoids some
weird and hard to diagnose problems that can occur in weirdly
restricted environments.
author | Augie Fackler <augie@google.com> |
---|---|
date | Fri, 20 Jan 2017 10:17:34 -0500 |
parents | 2d555d753f0e |
children | dab92f3dbd98 |
line wrap: on
line source
#require py3exe This test helps in keeping a track on which commands we can run on Python 3 and see what kind of errors are coming up. The full traceback is hidden to have a stable output. $ for cmd in version debuginstall ; do > echo $cmd > $PYTHON3 `which hg` $cmd 2>&1 2>&1 | tail -1 > done version warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. debuginstall TypeError: Can't convert 'bytes' object to str implicitly