Merge bitcoin/bitcoin#27471: test: fix bumpfee 'spend_one_input' occasional failure

[DashCoreAutoGuix]

Backport Details

Bitcoin Commit: 54e07a0
Bitcoin PR: bitcoin#27471
Version: 0.25
Batch: 412

Summary

This backport introduces the wallet_bumpfee.py functional test file from Bitcoin Core, including the fix for the 'spend_one_input' occasional failure.

Note: This PR adds the entire wallet_bumpfee.py test file (706 lines) because it doesn't exist yet in the batch branch. The Bitcoin commit 54e07a0 only modified 11 lines to fix a test ordering issue, but since the base file didn't exist, the cherry-pick brought in the complete file as it existed at that Bitcoin commit (with the fix already applied).

Changes

• Introduces test/functional/wallet_bumpfee.py with the fix already applied
• The fix moves test_feerate_checks_replaced_outputs to the end of the test suite to prevent it from consuming UTXOs needed by other subtests
• Adds proper setup (balance funding) to the moved test function

Dependencies

This test requires the bumpfee RPC functionality to be backported first. The test will not work until those RPC commands are available in Dash Core.

Original Bitcoin Description

Most of the subtests in wallet_bumpfee.py expect to find spendable UTXOs of 0.001 btc in the rbf wallet. They use the 'spend_one_input()' method which fails if none of them exist.

The sporadic failure comes from the recently added 'test_feerate_checks_replaced_outputs' subtest that can spend all them, leaving the next subtests with no 0.001 UTXOs to spend.

To solve it, this PR moves the recently added case into a "context independent subtests" section which is placed at the end to not affect other cases.

---

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

[coderabbitai]

Warning

Rate limit exceeded

@DashCoreAutoGuix has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 51 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 54e2588 and 88864ed.

📒 Files selected for processing (2)

• doc/developer-notes.md (1 hunks)
• test/functional/wallet_bumpfee.py (1 hunks)

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch backport-0.25-batch-412-pr-27471

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}