Any reason to test determinism separate from consistency? It should be ok to just move the assert_equal down a bit:
diff --git a/test/functional/feature_utxo_set_hash.py b/test/functional/feature_utxo_set_hash.py
index 233a0ccec7..d25803d883 100755
--- a/test/functional/feature_utxo_set_hash.py
+++ b/test/functional/feature_utxo_set_hash.py
@@ -25,20 +25,9 @@ class UTXOSetHashTest(BitcoinTestFramework):
self.log.info("Test deterministic UTXO set hash results")
node = self.nodes[0]
+ wallet = MiniWallet(node)
mocktime = node.getblockheader(node.getblockhash(0))['time'] + 1
node.setmocktime(mocktime)
- blocks = node.generatetoaddress(10, node.get_deterministic_priv_key().address)
-
- assert_equal(node.gettxoutsetinfo()['hash_serialized_2'], "9411e505b12619bc0d464ead3c2a14823f53d288380adf3742c7f86b64e3d6f1")
- assert_equal(node.gettxoutsetinfo("muhash")['muhash'], "75d363bf768ebe52102613792ceeb345364874b86f4579eb8030ff835799ecc9")
-
- node.invalidateblock(blocks[0])
-
- def test_muhash_implementation(self):
- self.log.info("Test MuHash implementation consistency")
-
- node = self.nodes[0]
- wallet = MiniWallet(node)
# Generate 100 blocks and remove the first since we plan to spend its
# coinbase
@@ -78,10 +67,11 @@ class UTXOSetHashTest(BitcoinTestFramework):
node_muhash = node.gettxoutsetinfo("muhash")['muhash']
assert_equal(finalized[::-1].hex(), node_muhash)
+ assert_equal(node.gettxoutsetinfo()['hash_serialized_2'], "5b1b44097406226c0eb8e1362cd17a1f346522cf9390a8175a57a5262cb1963f")
+ assert_equal(node.gettxoutsetinfo("muhash")['muhash'], "4b8803075d7151d06fad3e88b68ba726886794873fbfa841d12aefb2cc2b881b")
def run_test(self):
self.test_deterministic_hash_results()
- self.test_muhash_implementation()
if __name__ == '__main__':