rhg: show a bug where repeated [hg status] is needed to cache everything

tests/test-status.t

@@ -944,7 +944,7 b' It is still not set when there are unkno'
   $ hg debugdirstate --all --no-dates | grep '^ '
       0         -1 unset               subdir
 
-Now the directory is eligible for caching, so its mtime is save in the dirstate
+Now the directory is eligible for caching, so its mtime is saved in the dirstate
 
   $ rm subdir/unknown
   $ sleep 0.1 # ensure the kernel’s internal clock for mtimes has ticked
@@ -976,4 +976,35 b' Removing a node from the dirstate resets'
   $ hg status
   ? subdir/a
 
+Changing the hgignore rules makes us recompute the status (and rewrite the dirstate).
+
+  $ rm subdir/a
+  $ mkdir another-subdir
+  $ touch another-subdir/something-else
+
+  $ cat > "$TESTDIR"/extra-hgignore <<EOF
+  > something-else
+  > EOF
+
+  $ hg status --config ui.ignore.global="$TESTDIR"/extra-hgignore
+  $ hg debugdirstate --all --no-dates | grep '^ '
+      0         -1 set                 subdir
+
+  $ hg status
+  ? another-subdir/something-else
+
+  $ hg debugdirstate --all --no-dates | grep '^ '
+      0         -1 unset               subdir (known-bad-output !)
+
+For some reason the first [status] is not enough to save the updated
+directory mtime into the cache. The second invocation does it.
+The first call only clears the directory cache by marking the directories
+as "outdated", which seems like a bug.
+
+  $ hg status
+  ? another-subdir/something-else
+
+  $ hg debugdirstate --all --no-dates | grep '^ '
+      0         -1 set                 subdir
+
 #endif