view tests/test-rebase-dry-run.t @ 50353:c2a1f8668606 stable

chg: set CHGHG before connecting to command server

cf4d2f31 (!523) changed chg to set `CHGHG` itself when spawning a new command
server, in order to ensure that the path to the `hg` executable would be checked
during server validation. (This is useful when chg is built with `HGPATHREL`).

However, that change broke chg because it failed to set `CHGHG` before trying
to connect to an existing command server. This means that if `CHGHG` is not
present in the environment, chg will always spawn a new command server, entirely
negating the point of chg.

This breakage wasn't initially caught because of the difficulty of writing
automated tests with the `HGPATHREL` feature enabled, which meant the change
was only tested manually to make sure that it fixed the problem with `HGPATHREL`
that prompted the change.

In practice, this functionality is only really useful when chg is built with
`HGPATHREL`, so I considered wrapping it in an `#ifdef` to preserve the old
behavior by default. However, this makes it hard to write tests since one would
have to explicitly set `HGPATHREL=1` when running `run-tests.py` (which is why
the original change lacked tests). It would be great if there were a way of
testing features that are gated behind conditional compilation.

======================
rebase --dry-run tests
======================

Test behavior associated with `hg rebase --dry-run`

Setup
=====

  $ hg init r1
  $ cd r1
  $ echo one > f01.txt
  $ echo two > f02.txt
  $ echo three > f03.txt
  $ hg add
  adding f01.txt
  adding f02.txt
  adding f03.txt
  $ hg ci -m 'ci-1' f01.txt f02.txt f03.txt
  $ hg book base; hg book -i
  $ echo add-to-one >> f01.txt
  $ hg ci -m 'br-1' f01.txt
  $ hg book branch-1; hg book -i
  $ hg up base; hg book -i
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  (activating bookmark base)
  $ echo add-to-two >> f02.txt
  $ hg ci -m 'br-2' f02.txt
  created new head
  $ hg book branch-2; hg book -i
  $ hg up branch-1; hg book -i
  2 files updated, 0 files merged, 0 files removed, 0 files unresolved
  (activating bookmark branch-1)
  $ hg log -G
  o  changeset:   2:d408211b0a6f
  |  bookmark:    branch-2
  |  tag:         tip
  |  parent:      0:99418d161ee0
  |  user:        test
  |  date:        Thu Jan 01 00:00:00 1970 +0000
  |  summary:     br-2
  |
  | @  changeset:   1:ab62441498e5
  |/   bookmark:    branch-1
  |    user:        test
  |    date:        Thu Jan 01 00:00:00 1970 +0000
  |    summary:     br-1
  |
  o  changeset:   0:99418d161ee0
     bookmark:    base
     user:        test
     date:        Thu Jan 01 00:00:00 1970 +0000
     summary:     ci-1
  


Check the working copy changes do not get wiped out
===================================================

  $ echo add-to-three >> f03.txt

f03 is modified

  $ hg st
  M f03.txt
  $ hg diff
  diff -r ab62441498e5 f03.txt
  --- a/f03.txt	Thu Jan 01 00:00:00 1970 +0000
  +++ b/f03.txt	Thu Jan 01 00:00:00 1970 +0000
  @@ -1,1 +1,2 @@
   three
  +add-to-three


  $ hg rebase -v -n -s branch-2 -d branch-1 --config extensions.rebase=
  starting dry-run rebase; repository will not be changed
  rebasing 2:d408211b0a6f branch-2 tip "br-2"
  resolving manifests
  getting f02.txt
  committing files:
  f02.txt
  committing manifest
  committing changelog
  rebase merging completed
  dry-run rebase completed successfully; run without -n/--dry-run to perform this rebase

f03 changes are lost

  $ hg st
  M f03.txt
  $ hg diff
  diff -r ab62441498e5 f03.txt
  --- a/f03.txt	Thu Jan 01 00:00:00 1970 +0000
  +++ b/f03.txt	Thu Jan 01 00:00:00 1970 +0000
  @@ -1,1 +1,2 @@
   three
  +add-to-three