Patrick Lodder ae38534692
qa: add transaction download test
Tests 5 scenarios for transaction download scheduling:

1. Whether eventually, after a series of timeouts, all our peers
   that announced a transaction are sent a getdata request
2. Whether outbound peers are prioritized over inbound peers when
   a getdata request takes longer than optimal
3. That we honor the maximum in-flight capacity, that this is on
   a per-peer basis and that it resets itself after timeout
4. That when we have an inflight getdata request when a peer
   disconnects, we recover after the initial 30 second timeout
   and fetch the transaction from another peer
5. That we recover after a peer sends us a notfound message for
   a tx we had an inflight getdata request for.
2022-07-12 02:57:00 +02:00
..
2016-10-17 00:34:37 +08:00
2016-05-05 15:43:37 +02:00
2021-08-13 03:44:02 +02:00
2022-07-12 02:57:00 +02:00
2016-07-29 09:41:58 -04:00
2016-05-05 15:43:37 +02:00
2021-09-03 10:52:24 +01:00