Optimize breez-itest run time #548
Description
The breez-itest CI job is currently taking 40-50 minutes, which is too long. And it will only get worse as each test we add increases the time (tests run sequentially).
We should find some ways to speed it up in order to get quicker feedback.
One limitation to keep in mind is that many tests rely on the Spark regtest network. The faucet specifically has been known to throw rate limit errors if we try to run all tests in parallel.
Some ideas:
- Parallelization
- Run in parallel all tests that don't rely on the faucet
- Run the remaining tests with some but limited parallelization (as much as we can before hitting rate limits)
- Reuse seeds. Funding the wallet using the faucet adds time to each test, and all tests get funds individually. If we reuse some seeds across the same test suite run we should reduce run time significantly