They are already enabled by default for regtest:
qa: Remove redundant checkmempool/checkblockindex extra_args #13913
pull MarcoFalke wants to merge 1 commits into bitcoin:master from MarcoFalke:Mf1808-qaRedundantChecks changing 5 files +4 −8-
MarcoFalke commented at 6:39 PM on August 8, 2018: member
-
qa: Remove redundant checkmempool/checkblockindex extra_args fa31ca0c22
- MarcoFalke added the label Tests on Aug 8, 2018
-
Empact commented at 11:27 PM on August 8, 2018: member
Concept ACK. Could be interesting to disable these settings and see which tests require them.
-
-
Empact commented at 7:37 AM on August 11, 2018: member
utACK fa31ca0 @domob1812 I'm not that familiar with the checks, e.g. wrt to whether they have any side-effects, so I was curious to explore the counterfactual - if the checks are explicitly active now, and removing the explicit activation leaves them active by default, what happens if the default changes? Ran the affected tests with regtest
fDefaultConsistencyChecks = false, and each passed, so seems good to me. - MarcoFalke merged this on Aug 11, 2018
- MarcoFalke closed this on Aug 11, 2018
- MarcoFalke referenced this in commit a08533c1a0 on Aug 11, 2018
- MarcoFalke deleted the branch on Aug 11, 2018
- PastaPastaPasta referenced this in commit 81bf95e464 on Jun 27, 2021
- PastaPastaPasta referenced this in commit 23417499e0 on Jun 28, 2021
- PastaPastaPasta referenced this in commit 5edf4694d4 on Jun 29, 2021
- PastaPastaPasta referenced this in commit d42488ea69 on Jun 29, 2021
- PastaPastaPasta referenced this in commit fa5755785b on Jun 29, 2021
- PastaPastaPasta referenced this in commit f33c2c8101 on Jun 29, 2021
- PastaPastaPasta referenced this in commit b04090df10 on Jun 29, 2021
- MarcoFalke locked this on Sep 8, 2021
