Change Details

The alias approach is poorly inherited by other process spawned during the test. So use the same approach as for `python`/`python3` we write a file explicitly. Doing this fixes `which hg` calls to point at the same location as `hg` Using chg server side has some minor effect of some stdout/stderr ordering when using `chg` as the server too on python.

The alias approach is poorly inherited by other process that the test might spawn. To solve this we use the same approach as for `python`/`python3` we write an executable file explicitly. Doing this fixes `which hg` invocation that now returns the same location as `hg`. Using chg server side has some minor effect on some stdout/stderr ordering when using `chg` as the server too.

The alias approach is poorly inherited by other process spawned during the testthat the test might spawn. SoTo solve this we use the same approach as for `python`/`python3` we write aan executable file explicitly. Doing this fixes `which hg` calls to point atinvocation that now returns the same location as `hg`. Using chg server side has some minor effect ofon some stdout/stderr ordering when using `chg` as the server too on python.