diff options
| author | Carl Hetherington <cth@carlh.net> | 2022-09-04 21:26:24 +0200 |
|---|---|---|
| committer | Carl Hetherington <cth@carlh.net> | 2022-09-05 23:52:03 +0200 |
| commit | b5cd81225e49fc983777dbf15a38e262fb2dd9f6 (patch) | |
| tree | 8bff752b3fbb726133dec69f85de3142bd2bb681 /test | |
| parent | f5bd787fb71466a6187050086b2890b9b0ac9294 (diff) | |
Let config/cinemas/dkdm_recipients take care of their own recovery.
This should mean that if one fails to load, but the others are OK,
we don't re-write everything. I hope this has no bad side-effects
that I didn't think of.
It's particularly helpful in the case of #2319 where a failure to
load cinemas.xml (which was being created by another tool) caused
the config to be re-written, breaking all existing DKDMs.
Diffstat (limited to 'test')
| -rw-r--r-- | test/config_test.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/config_test.cc b/test/config_test.cc index 687bea956..fc3a27601 100644 --- a/test/config_test.cc +++ b/test/config_test.cc @@ -215,7 +215,7 @@ BOOST_AUTO_TEST_CASE (config_keep_cinemas_if_making_new_config) boost::filesystem::remove (dir / "2.16" / "config.xml"); Config::instance(); - check_text_file (dir / "backup_for_test.xml", dir / "cinemas.xml.1"); + check_text_file(dir / "backup_for_test.xml", dir / "cinemas.xml"); } |