diff options
author | Sebastian Falbesoner <sebastian.falbesoner@gmail.com> | 2022-06-29 17:51:39 +0200 |
---|---|---|
committer | Sebastian Falbesoner <sebastian.falbesoner@gmail.com> | 2022-06-29 18:05:59 +0200 |
commit | 475aae846e71e355e8f70c0a1857339b1124bcc0 (patch) | |
tree | 90d9e9b163ecac9cd2aa4675e228a7ccd081fd0c /test/functional/feature_maxuploadtarget.py | |
parent | b1ba3ed155e89fb6e30237cba8bc8028c7906830 (diff) | |
download | bitcoin-475aae846e71e355e8f70c0a1857339b1124bcc0.tar.xz |
test: pass `datacarriersize` option for tests using large outputs (instead of `acceptnonstdtxn`)
By specifying the `datacarriersize` option instead of the more
generic `acceptnonstdtxn`, we can be more specific about what
part of the transaction is non-standard and can be sure that all
other aspects follow the standard policy.
Diffstat (limited to 'test/functional/feature_maxuploadtarget.py')
-rwxr-xr-x | test/functional/feature_maxuploadtarget.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/functional/feature_maxuploadtarget.py b/test/functional/feature_maxuploadtarget.py index 0b9d651226..3ea412002a 100755 --- a/test/functional/feature_maxuploadtarget.py +++ b/test/functional/feature_maxuploadtarget.py @@ -46,7 +46,7 @@ class MaxUploadTest(BitcoinTestFramework): self.num_nodes = 1 self.extra_args = [[ "-maxuploadtarget=800M", - "-acceptnonstdtxn=1", + "-datacarriersize=100000", ]] self.supports_cli = False |