As per title. Add CTOR ordering to test block construction. Use NULLDUMMY
instead of CLEANSTACK for checking consensus vs non-consensus script cache behavior.
Details
Details
- Reviewers
deadalnix jasonbcox - Group Reviewers
Restricted Project - Commits
- rSTAGING5a97f9ae4add: [tests] Fix checkinputs_test to work under magnetic anomaly
rABC5a97f9ae4add: [tests] Fix checkinputs_test to work under magnetic anomaly
make -j10 VERBOSE=1 check
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- fucked-tests
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 3976 Build 6024: Bitcoin ABC Buildbot (legacy) Build 6023: arc lint + arc unit
Event Timeline
Comment Actions
I'm sure I missed some of the feedback provided on D2089 .
src/test/txvalidationcache_tests.cpp | ||
---|---|---|
22 ↗ | (On Diff #5907) | Remove |
182 ↗ | (On Diff #5907) | Seems like a temporary would be beneficial here |
186 ↗ | (On Diff #5907) | Why is that called p2sh if it is not p2sh ? |
194 ↗ | (On Diff #5907) | The whole block should be scoped |
196 ↗ | (On Diff #5907) | Fix comment |
src/test/txvalidationcache_tests.cpp | ||
---|---|---|
249 ↗ | (On Diff #5907) | DERSIG -> NULLDUMMY |
src/test/txvalidationcache_tests.cpp | ||
---|---|---|
170 | double space after Create |
src/test/txvalidationcache_tests.cpp | ||
---|---|---|
180 | Scope should start before this line imo. There's no reason to have the mutableFunding_tx stuff inside this scope, right? |
src/test/txvalidationcache_tests.cpp | ||
---|---|---|
180 | It doesn't change anything. But it groups things logically. Ehter way it is fine. |