diff options
| author | Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> | 2019-01-14 13:40:00 +0200 |
|---|---|---|
| committer | Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> | 2019-01-30 07:17:22 +0200 |
| commit | 6f6514a08090b37b5e8c086015ee4881813ef867 (patch) | |
| tree | a81c889c45f5e972229d024ef8c97308312d6336 /test | |
| parent | 84d0fdce11709c8e26b9c450d47727ab36641437 (diff) | |
Correct units for "-dbcache" and "-prune"
All dbcache-related values in the code are measured in MiB (not in
megabytes, MB) or in bytes.
The GUI "-prune" values in GB are translated to the node values in MiB
correctly. The maximum of the "-prune" QSpinBox is not limited by the
default value of 99 (GB).
Also, this improves log readability.
Diffstat (limited to 'test')
| -rwxr-xr-x | test/functional/feature_pruning.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/functional/feature_pruning.py b/test/functional/feature_pruning.py index 9a3f4fae45..3e1ba88f0a 100755 --- a/test/functional/feature_pruning.py +++ b/test/functional/feature_pruning.py @@ -320,7 +320,7 @@ class PruneTest(BitcoinTestFramework): if has_block(3): raise AssertionError("blk00003.dat is still there, should be pruned by now") - # stop node, start back up with auto-prune at 550MB, make sure still runs + # stop node, start back up with auto-prune at 550 MiB, make sure still runs self.stop_node(node_number) self.start_node(node_number, extra_args=["-prune=550"]) |