wallet_taproot.py fails with "Insufficient funds (-4)" #25030

 test  2022-04-29T13:16:35.409000Z TestFramework (ERROR): JSONRPC error 
                                   Traceback (most recent call last):
                                     File "/private/var/folders/xx/vl5f934s6k927z1vyyl9cxth0000gn/T/cirrus-ci-build/ci/scratch/build/bitcoin-x86_64-apple-darwin/test/functional/test_framework/test_framework.py", line 133, in main
                                       self.run_test()
                                     File "/private/var/folders/xx/vl5f934s6k927z1vyyl9cxth0000gn/T/cirrus-ci-build/ci/scratch/build/bitcoin-x86_64-apple-darwin/test/functional/wallet_taproot.py", line 448, in run_test
                                       psbt = self.psbt_online.walletcreatefundedpsbt([], [{self.boring.getnewaddress(): self.psbt_online.getbalance()}], None, {"subtractFeeFromOutputs": [0]})['psbt']
                                     File "/private/var/folders/xx/vl5f934s6k927z1vyyl9cxth0000gn/T/cirrus-ci-build/ci/scratch/build/bitcoin-x86_64-apple-darwin/test/functional/test_framework/coverage.py", line 49, in __call__
                                       return_val = self.auth_service_proxy_instance.__call__(*args, **kwargs)
                                     File "/private/var/folders/xx/vl5f934s6k927z1vyyl9cxth0000gn/T/cirrus-ci-build/ci/scratch/build/bitcoin-x86_64-apple-darwin/test/functional/test_framework/authproxy.py", line 144, in __call__
                                       raise JSONRPCException(response['error'], status)
                                   test_framework.authproxy.JSONRPCException: Insufficient funds (-4)

https://cirrus-ci.com/task/5522204518514688?logs=ci#L1609

Was this bug fixed?

No idea. I am just doubting how useful it is to keep track of low-frequency intermittent test issues when even high-frequent ones remain unfixed for months/years.

Fair enough. Where are the high frequent test issues listed? In the good first issues somewhere? Perhaps the situation could be improved if it was clear which ones should be prioritized. (There seems to be at least a couple of existing contributors who are regularly improving the functional tests.) Like everyone I get occasional intermittent issues but I have no idea if they are low frequency or high frequency generally for others on the project or not.

I keep track of them myself, but there is also a "dashboard" (not public) where some people have access.

One could also look at the red stuff in https://cirrus-ci.com/github/bitcoin/bitcoin/master

I think the best way to keep track of them is by creating an issue here and updating it with an exponential backoff if it still occurs. (After 2 weeks, 4 weeks, 2 months, 4 months ...)

This is still happening daily.

@MarcoFalke: Fixed in #25159?