Looks like it is somewhat slow (c.f. https://cirrus-ci.com/task/6602192649453568?logs=ci#L5401), so it would be nice to make it faster.
Possibly with txgraph, see https://github.com/bitcoin-core/qa-assets/pull/227#issuecomment-3032434420
Looks like it is somewhat slow (c.f. https://cirrus-ci.com/task/6602192649453568?logs=ci#L5401), so it would be nice to make it faster.
Possibly with txgraph, see https://github.com/bitcoin-core/qa-assets/pull/227#issuecomment-3032434420
Interested in working on speeding up the mini_miner fuzz target. Are you already on this, or should I take a stab at it?
I am not. If you want to work on something, you can just do it without asking. In case there are two pull requests for the same thing, the authors should be glad about it, because they should be qualified to review each others pull request and pick the one that is more suitable to be merged.
Looks like it is somewhat slow (c.f. https://cirrus-ci.com/task/6602192649453568?logs=ci#L5401), so it would be nice to make it faster.
Possibly with txgraph, see bitcoin-core/qa-assets#227 (comment)
Can you close this now?
No, this is still an issue. See here: #33425 (comment). mini_miner is running for ~half an hour. cc @murchandamus @glozow
Unsure what the best course of action is, since the plan is to reimplement MiniMiner anyway after #28676. If there's a timeout/infinite loop then that's a bug we should fix for current wallet users. But if it's just a slow test, then I'd suggest leaving it as is and it will probably fix itself when mempool is more efficient at cluster calculation.
I haven't looked into the input itself (idk if @enirox001 or somebody wants to do it) but if the culprit is just too many potential outpoints then we can knock that down as an intermediate fix.