Since we just check if the -chronikscripthashindex init flag is unset to return a 400 error, this test was not actually checking that index is wiped the first time the flag is unset. We could be returning that error even with the index still intact on disk.
We can at least check the presence of the relevant log line to verify that we hit the function that is supposed to wipe the index..
Details
Details
- Reviewers
Fabien - Group Reviewers
Restricted Project - Commits
- rABCe8e4f82ea3a6: [chronik] test for the "Wiping existing scripthash index" log message
ninja check-functional
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- master
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 31370 Build 62238: Build Diff build-clang · build-diff · build-debug · build-clang-tidy · build-without-wallet Build 62237: arc lint + arc unit