Open
Description
Documenting flaky tests
- Most flaky tests are related to concurrency and how soon the node gets running, system resources and minor timing effects due to it. However, documenting them as we can aim to fix it and not ensure we don't end up adding new ones to it.
- Majority of them can be re-created with varying concurrency with
MAKE_JOBS=32/64/128/256
etc, and also selecting different numbers or tests at random, and/or limiting resources with cgroups.
Wide spectrum
- [Fixed] Failing to start and get nodes responsive in time: tests: better resilience for concurrent node starts #3011 aims to fix majority of that. But there might still be a few that still persists.
Localized
wallet_txn_doublespend.py
- This checks for initial block download and fails. If we loop through it to wait for longer, this should be fixed.
feature_token_merge.py
- This seems to be something in test that's out of sync
test_framework.authproxy.JSONRPCException: Test AddPoolLiquidityTx execution failed:
tx must have at least one input from account owner (-32600)
feature_evm_gas.py
- TODO
rpc_getcustomtx.py
- Hits line 66: assert_equal(result["valid"], True) fails when there's high concurrency
- [Fixed] Ubuntu 24.04 related: tests: fix flaky tests that fail due to type strictness #3010
feature_loan_basics.py
feature_evm_contracts.py
feature_loan_low_interest.py