diff options
| author | fanquake <fanquake@gmail.com> | 2023-10-02 11:44:42 +0200 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-10-02 11:57:56 +0200 |
| commit | e3b052800f61abcb7d19d1a35fa04c195f3503ab (patch) | |
| tree | 5cc96802d3824793821a6e7777f0d662d8c6050a /src | |
| parent | 8b44d011184c7d807bc6e61107116ed05c45b8d1 (diff) | |
| parent | 2ab7952bda8d15e91b03f8307839030cbb55614e (diff) | |
| download | bitcoin-e3b052800f61abcb7d19d1a35fa04c195f3503ab.tar.xz | |
Merge bitcoin/bitcoin#28227: test: check for specific bip157 disconnect reasons, add test coverage
2ab7952bda8d15e91b03f8307839030cbb55614e test: add bip157 coverage for (start height > stop height) disconnect (Sebastian Falbesoner)
63e90e1d3f5ed08f9871f07667d389ec66aa621c test: check for specific disconnect reasons in p2p_blockfilters.py (Sebastian Falbesoner)
Pull request description:
This PR checks for specific disconnect reasons using `assert_debug_log` in the functional test `p2p_blockfilters.py`. With that we ensure that the disconnect happens for the expected reason and also makes it easier to navigate between implementation and test code, i.e. both the questions "do we have test coverage for this disconnect cause?" (from an implementation reader's perspective) and "where is the code handling this disconnect cause?" (from a test reader's perspective) can be answered simply by grep-ping the corresponding debug message.
Also, based on that, missing coverage for the (start height > stop height) disconnect case is added:
https://github.com/bitcoin/bitcoin/blob/b7138252ace6d21476964774e094ed1143cd7a1c/src/net_processing.cpp#L3050-L3056
ACKs for top commit:
MarcoFalke:
lgtm ACK 2ab7952bda8d15e91b03f8307839030cbb55614e
furszy:
Looks good, code ACK 2ab7952b
Tree-SHA512: 0581cb569d5935aaa004a95a6f16eeafe628b9d816ebb89232f2832e377049df878a1e74c369fb46931b94e1a3a5e3f4aaa21a007c0a488f4ad2cda0919c605d
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions