AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

pytest: make pay tests more robust.

Public commit record

What the developer wrote

Authored by Rusty Russell

78/100 · Adequate
pytest: make pay tests more robust.

1. Don't assume they send group 0 (thus waitsendpay works). waitsendpay should be unnecessary
after pay anyway.
2. Don't use pay for test_multichan_stress, since it relies on pay not learning that
the channel is unreliable.
3. Use xpay for test_listhtlcs_wait, since we want no shadow.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit only changes test code in the Core Lightning project's test suite. It makes three payment-related tests more robust by removing unnecessary wait calls, switching from high-level 'pay' to lower-level 'sendpay' in one stress test, and using 'xpay' with shadow routes disabled in another. There are no changes to production code, no bug fixes, and no security-relevant behavior changes.

Recommended action

No security action required. This is a test-maintenance commit. Reviewers may optionally verify that the updated tests still exercise the intended production paths.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.