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

MarcoFalke commented at 2:23 pm on April 29, 2022: member

 0 test  2022-04-29T13:16:35.409000Z TestFramework (ERROR): JSONRPC error 
 1                                   Traceback (most recent call last):
 2                                     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
 3                                       self.run_test()
 4                                     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
 5                                       psbt = self.psbt_online.walletcreatefundedpsbt([], [{self.boring.getnewaddress(): self.psbt_online.getbalance()}], None, {"subtractFeeFromOutputs": [0]})['psbt']
 6                                     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__
 7                                       return_val = self.auth_service_proxy_instance.__call__(*args, **kwargs)
 8                                     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__
 9                                       raise JSONRPCException(response['error'], status)
10                                   test_framework.authproxy.JSONRPCException: Insufficient funds (-4)

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

MarcoFalke added the label Bug on Apr 29, 2022

MarcoFalke added the label Tests on Apr 29, 2022

MarcoFalke closed this on May 12, 2022

michaelfolkson commented at 12:48 pm on May 12, 2022: contributor

Was this bug fixed?

MarcoFalke commented at 12:59 pm on May 12, 2022: member

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.

michaelfolkson commented at 1:11 pm on May 12, 2022: contributor

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.

MarcoFalke commented at 1:21 pm on May 12, 2022: member

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 …)

MarcoFalke commented at 1:23 pm on May 16, 2022: member

This is still happening daily.

michaelfolkson commented at 8:41 pm on May 18, 2022: contributor

@MarcoFalke: Fixed in #25159?

DrahtBot locked this on May 18, 2023

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