Mercurial > hg
view tests/test-push-http.out @ 6262:de7256c82fad
hgweb: clarify which address and port can/cannot be bound at startup (bug 769)
The error message at startup when the address/port could not be bound
was confusing:
hg serve
abort: cannot start server: Address already in use
Be more explicit:
$ hg serve -a localhost
abort: cannot start server at 'localhost:8000': Address already in use
Also be more explicit on success, showing hostname and ip address/port:
$ hg -v serve -a localhost -p 80
listening at http://localhost/ (127.0.0.1:80)
We are careful to handle a missconfigured machine whose hostname does not
resolve, falling back to the address given at the command line.
Remove a dead-code error message.
author | Stephen Deasey <sdeasey@gmail.com> |
---|---|
date | Mon, 10 Mar 2008 19:25:34 +0000 |
parents | f53b9a383476 |
children | e29557d687c9 |
line wrap: on
line source
adding a 1 files updated, 0 files merged, 0 files removed, 0 files unresolved % expect ssl error pushing to http://localhost/ searching for changes ssl required % serve errors % expect authorization error pushing to http://localhost/ searching for changes push not authorized % serve errors % expect authorization error: must have authorized user pushing to http://localhost/ searching for changes push not authorized % serve errors % expect success pushing to http://localhost/ searching for changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files % serve errors changegroup hook: HG_NODE=ba677d0156c1196c1a699fa53f390dcfc3ce3872 HG_SOURCE=serve HG_URL=remote:http rolling back last transaction % expect authorization error: all users denied pushing to http://localhost/ searching for changes push not authorized % serve errors % expect authorization error: some users denied, users must be authenticated pushing to http://localhost/ searching for changes push not authorized % serve errors