# HG changeset patch
# User Martin von Zweigbergk <martinvonz@google.com>
# Date 1606950916 28800
# Node ID d767f71b91589335041b570ec60281a3a06ab117
# Parent  ecef004c64103535be484cd98ce8d4b6cd6f442a
tests: show that in-memory rebase leaves state when working copy is dirty

When in-memory rebase falls back to on-disk rebase, it checks if the
working copy is dirty. If it is, it aborts the rebase. However, it
leaves the rebase state on disk. I broke it in feffeb18d412 (rebase:
teach in-memory rebase to not restart with on-disk rebase on conflict,
2020-09-18).

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

diff -r ecef004c6410 -r d767f71b9158 tests/test-rebase-inmemory.t
--- a/tests/test-rebase-inmemory.t	Fri Nov 27 18:32:20 2020 +0530
+++ b/tests/test-rebase-inmemory.t	Wed Dec 02 15:15:16 2020 -0800
@@ -487,6 +487,14 @@
   [20]
   $ cat a
   dirty
+  $ hg status -v
+  M a
+  # The repository is in an unfinished *rebase* state.
+  
+  # To continue:    hg rebase --continue
+  # To abort:       hg rebase --abort
+  # To stop:        hg rebase --stop
+  
 
 Retrying without in-memory merge won't lose merge state
   $ cd ..