# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@octobus.net>
# Date 1676313999 -3600
# Node ID 09367b3d23d89b6ac62d85b7764d2f0c57eda4ce
# Parent  1e6015ddf6984caaad3ae2efb0643137cc7a7a13
test: explicitly "add" file before some commit in test-filecache.py

`hg commit -A` will revert the `hg addremove` step if the commit fails. However
`hg rollback` currently does not.

We are about to improve internal consistency around transaction and dirstate and the behavior of `hg rollback` will align on the other behavior in the process.

Before doing so, we make sure the test is using a separate call to `hg add` to
avoid the test scenario to be affected by that future change.

note: the behavior change for `hg rollback` seems fine as it affect a niche
usecase and `hg rollback` usage have been strongly discouraged for a while.

diff -r 1e6015ddf698 -r 09367b3d23d8 tests/test-filecache.py
--- a/tests/test-filecache.py	Mon Feb 13 17:42:10 2023 +0100
+++ b/tests/test-filecache.py	Mon Feb 13 19:46:39 2023 +0100
@@ -165,7 +165,7 @@
 
 def test_filecache_synced():
     # test old behavior that caused filecached properties to go out of sync
-    os.system('hg init && echo a >> a && hg ci -qAm.')
+    os.system('hg init && echo a >> a && hg add a && hg ci -qm.')
     repo = hg.repository(uimod.ui.load())
     # first rollback clears the filecache, but changelog to stays in __dict__
     repo.rollback()