view relnotes/5.2 @ 46327:85c0c7145f8e

run-tests: catch a Windows specific error when testing for a free socket

I'm not sure why this only happens with py3, but this error code doesn't map to
any of the 3 currently being handled, and kills `run-tests.py` before it can run
any tests when it happens:

    OSError: [WinError 10013] An attempt was made to access a socket in a way
    forbidden by its access permissions

The documentation[1] says this can happen if another process is bound to the
address with exclusive access.  This seems to keep it happy.

[1] https://docs.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2

Differential Revision: https://phab.mercurial-scm.org/D9816

== New Features ==

 * The amend extension supports the `--currentuser` argument.

 * The amend extension supports the `--close-branch` argument.

 * The amend extension supports the `--secret` argument.

 * The uncommit extension supports the `rewrite.update-timestamp` config option.

== New Experimental Features ==


== Bug Fixes  ==


== Backwards Compatibility Changes ==

 * A shell that supports `$(command)`` syntax for command substitution is now
   required for running the test suite. The test runner normally uses
   `sh`, so if that is a shell that doesn't support `$(command)` syntax,
   you can override it by setting `$HGTEST_SHELL` or by passing it to
   `run-tests.py --shell <shell>`.

 * The (experimental) narrow extension's wire protocol changed. If
   you're using it, you'll need to make sure to upgrade server and
   client at the same time.

== Internal API Changes ==