pytest: fix flake in reckless install timeout.
What changed, and why it matters
This commit is a test-only change. It skips one pytest test when the code is being run under Valgrind on a slow machine, because the test's 15-second timeout was sometimes exceeded in CI. There is no security issue in the actual Core Lightning software.
No security action needed. This is a CI/test flakiness fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch adds a @unittest.skipIf(VALGRIND and SLOW_MACHINE, ...) decorator to test_reckless_uv_install in tests/test_reckless.py. The test installs a plugin via the reckless tool and then starts it with lightning-cli plugin start. Under Valgrind on slow CI runners, lightning-cli can take longer than reckless’s hard-coded 15-second timeout, causing a flaky failure. The fix simply avoids running this timing-sensitive test in that configuration. No product code is changed.
Changed components
tests/test_reckless.pyInspect captured patch +2 / −1
diff --git a/tests/test_reckless.py b/tests/test_reckless.py
index 64efa6ab..10ade362 100644
--- a/tests/test_reckless.py
+++ b/tests/test_reckless.py
@@ -2,7 +2,7 @@ from fixtures import * # noqa: F401,F403
import subprocess
from pathlib import PosixPath, Path
import socket
-from pyln.testing.utils import VALGRIND
+from pyln.testing.utils import VALGRIND, SLOW_MACHINE
import pytest
import os
import re
@@ -351,6 +351,7 @@ def test_tag_install(node_factory):
header = line
+@unittest.skipIf(VALGRIND and SLOW_MACHINE, "node too slow for starting plugin under valgrind")
def test_reckless_uv_install(node_factory):
node = get_reckless_node(node_factory)
node.start()
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.