tests: mark tests that fail when using chg as #require no-chg
As far as I can tell, most of these failures are due to using $HGPORT, which it seems chg might be using itself? I don't know enough to debug these failures to fix them properly. Differential Revision: https://phab.mercurial-scm.org/D3562
Showing
- tests/test-clone-uncompressed.t 1 addition, 1 deletiontests/test-clone-uncompressed.t
- tests/test-clonebundles.t 1 addition, 1 deletiontests/test-clonebundles.t
- tests/test-http-api-httpv2.t 2 additions, 0 deletionstests/test-http-api-httpv2.t
- tests/test-http-api.t 2 additions, 0 deletionstests/test-http-api.t
- tests/test-http-protocol.t 2 additions, 0 deletionstests/test-http-protocol.t
- tests/test-lfs-largefiles.t 1 addition, 1 deletiontests/test-lfs-largefiles.t
- tests/test-lfs-serve-access.t 1 addition, 1 deletiontests/test-lfs-serve-access.t
- tests/test-lfs-serve.t 1 addition, 1 deletiontests/test-lfs-serve.t
- tests/test-lfs-test-server.t 1 addition, 1 deletiontests/test-lfs-test-server.t
- tests/test-lfs.t 1 addition, 1 deletiontests/test-lfs.t
- tests/test-parseindex.t 2 additions, 0 deletionstests/test-parseindex.t
- tests/test-pull-bundle.t 2 additions, 0 deletionstests/test-pull-bundle.t
- tests/test-push-http.t 2 additions, 0 deletionstests/test-push-http.t
- tests/test-ssh-proto.t 2 additions, 0 deletionstests/test-ssh-proto.t
- tests/test-wireproto-command-capabilities.t 2 additions, 0 deletionstests/test-wireproto-command-capabilities.t
Loading
Please register or sign in to comment