diff options
| author | furszy <matiasfurszyfer@protonmail.com> | 2024-01-09 09:54:49 -0300 |
|---|---|---|
| committer | furszy <matiasfurszyfer@protonmail.com> | 2024-01-22 10:50:03 -0300 |
| commit | 966f5de99a9f5da05c91378ad1e8ea8ed37ac3b3 (patch) | |
| tree | 8d1d6abefc908ec6dd83391553477f6349b02cc1 /test | |
| parent | 03752444cd54df05a731557968d5a9f33a55c55c (diff) | |
| download | bitcoin-966f5de99a9f5da05c91378ad1e8ea8ed37ac3b3.tar.xz | |
init: improve corrupted/empty settings file error msg
The preceding "Unable to parse settings file" message lacked
the necessary detail and guidance for users on what steps to
take next in order to resolve the startup error.
Co-authored-by: Ryan Ofsky <ryan@ofsky.org>
Diffstat (limited to 'test')
| -rwxr-xr-x | test/functional/feature_settings.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/functional/feature_settings.py b/test/functional/feature_settings.py index 1bacdd447a..4175699152 100755 --- a/test/functional/feature_settings.py +++ b/test/functional/feature_settings.py @@ -53,7 +53,7 @@ class SettingsTest(BitcoinTestFramework): # Test invalid json with settings.open("w") as fp: fp.write("invalid json") - node.assert_start_raises_init_error(expected_msg='Unable to parse settings file', match=ErrorMatch.PARTIAL_REGEX) + node.assert_start_raises_init_error(expected_msg='does not contain valid JSON. This is probably caused by disk corruption or a crash', match=ErrorMatch.PARTIAL_REGEX) # Test invalid json object with settings.open("w") as fp: |