Update weird way to check for MTP in functional tests
ClosedPublic
Actions

Authored by deadalnix on Feb 9 2020, 21:50.

Details

Reviewers

Group Reviewers

Restricted Project

Commits

rSTAGINGe035b46366e4: Update weird way to check for MTP in functional tests
rABCe035b46366e4: Update weird way to check for MTP in functional tests

Summary

I noticed that some of our tests check for MTP in a strange way. This updates them to do so in a more straightforward fashion.

Test Plan

./test/functional/test_runner.py abc-mempool-coherence-on-activations abc-replay-protection

Diff Detail

Repository

rABC Bitcoin ABC

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

deadalnix created this revision.Feb 9 2020, 21:50

Herald added a reviewer: Restricted Project. · View Herald TranscriptFeb 9 2020, 21:50

Build Bitcoin-ABC / Diffs / Diff Testing started.

Build Bitcoin-ABC / Diffs / Diff Testing passed.

Harbormaster completed remote builds in B9374: Diff 16195.Feb 9 2020, 21:59

markblundeberg accepted this revision.Feb 10 2020, 00:37

This revision is now accepted and ready to land.Feb 10 2020, 00:37

Closed by commit rABCe035b46366e4: Update weird way to check for MTP in functional tests (authored by deadalnix). · Explain WhyFeb 10 2020, 13:02

This revision was automatically updated to reflect the committed changes.

deadalnix added a commit: rABCe035b46366e4: Update weird way to check for MTP in functional tests.

deadalnix added a commit: rSTAGINGe035b46366e4: Update weird way to check for MTP in functional tests.Apr 7 2020, 22:55

Revision Contents
Changeset List

Path

Size

test/

functional/

abc-mempool-coherence-on-activations.py

10 lines

abc-replay-protection.py

10 lines

Diff 16210

View Options

test/functional/abc-mempool-coherence-on-activations.py