pytest: mark test_partial_payment_restart slow.
What changed, and why it matters
This commit only adds a 'slow_test' marker to an existing test. The test was sometimes failing under valgrind because the simulated network was too slow and a multi-part payment timed out before the test could complete. This is a test-suite reliability fix, not a security fix in the actual lightning node software.
No security action required. This is a test categorization change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds @pytest.mark.slow_test to test_partial_payment_restart in tests/test_pay.py. The commit message explains that under valgrind the test runs slowly enough that a 60-second MPP timeout fires before waitsendpay returns, causing an RPC error WIRE_MPP_TIMEOUT. Marking the test slow moves it to a slower test category so it is not run in fast CI configurations. No production code is changed.
Changed components
tests/test_pay.pyInspect captured patch +1 / −0
diff --git a/tests/test_pay.py b/tests/test_pay.py
index d7012193..f73262c4 100644
--- a/tests/test_pay.py
+++ b/tests/test_pay.py
@@ -3310,6 +3310,7 @@ def test_partial_payment_timeout(node_factory, bitcoind):
l2.daemon.wait_for_log(r'HTLC set contains 2 HTLCs, for a total of 1000msat out of 1000msat \(payment_secret\)')
+@pytest.mark.slow_test
def test_partial_payment_restart(node_factory, bitcoind):
"""Test that we recover a set when we restart"""
l1, l2, l3 = node_factory.line_graph(3, wait_for_announce=True,
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.