Update sendtoaddress documention. Added missing lock. (#385) #488
GitHub Actions / ARM 64-bit
failed
Aug 2, 2024 in 0s
362 tests run, 361 passed, 0 skipped, 1 failed.
Annotations
Check failure on line 1 in wallet_tests
github-actions / ARM 64-bit
wallet_tests.rescan
failure
Raw output
ASSERTION FAILURE:
- file : wallet_tests.cpp
- line : 342
- message: check response . write() == tfm::format("[{\"success\":false,\"error\":{\"code\":-1,\"message\":\"Rescan failed for key with creation " "timestamp %d. There was an error reading a block from time %d, which is after or within %d " "seconds of key creation, and could contain transactions pertaining to the key. As a result, " "transactions and coins using this key may not appear in the wallet. This error could be caused " "by pruning or data corruption (see raptoreumd log for details) and could be dealt with by " "downloading and rescanning the relevant blocks (see -reindex and -rescan " "options).\"}},{\"success\":true}]", 0, oldTip->GetBlockTimeMax(), TIMESTAMP_WINDOW) has failed [[{"success":false,"error":{"code":-1,"message":"Rescan failed for key with creation timestamp 0. There was an error reading a block from time 1722577179, which is after or within 900 seconds of key creation, and could contain transactions pertaining to the key. As a result, transactions and coins using this key may not appear in the wallet. This error could be caused by pruning or data corruption (see raptoreumd log for details) and could be dealt with by downloading and rescanning the relevant blocks (see -reindex and -rescan options)."}},{"success":true}] != [{"success":false,"error":{"code":-1,"message":"Rescan failed for key with creation timestamp 0. There was an error reading a block from time 1722577178, which is after or within 900 seconds of key creation, and could contain transactions pertaining to the key. As a result, transactions and coins using this key may not appear in the wallet. This error could be caused by pruning or data corruption (see raptoreumd log for details) and could be dealt with by downloading and rescanning the relevant blocks (see -reindex and -rescan options)."}},{"success":true}]]
Loading