diff options
author | MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz> | 2023-01-24 12:24:04 +0100 |
---|---|---|
committer | MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz> | 2023-01-24 12:24:09 +0100 |
commit | 75e752f13492d4c373873fb4fc532e919d6082ad (patch) | |
tree | 80962b3e1337a1e105698ef944901ef8cc5e6ca7 /src | |
parent | fcff639af137f2a6636ef454d0404b969ab7772e (diff) | |
parent | fa952fad2fca833357e61a7bb8c76c2877b522f9 (diff) | |
download | bitcoin-75e752f13492d4c373873fb4fc532e919d6082ad.tar.xz |
Merge bitcoin/bitcoin#26954: test: Avoid rpc timeout in p2p_headers_sync_with_minchainwork
fa952fad2fca833357e61a7bb8c76c2877b522f9 test: Avoid rpc timeout in p2p_headers_sync_with_minchainwork (MarcoFalke)
Pull request description:
When running a lot of tests in parallel, I get `JSONRPCException: 'generatetoaddress' RPC took longer than 30.000000 seconds.`
The general recommendation, if running into timeouts, is to increase the `--timeout-factor`. However, I think that the default timeout values should be suitable to run the tests out of the box on reasonable hardware.
ACKs for top commit:
fanquake:
ACK fa952fad2fca833357e61a7bb8c76c2877b522f9
Tree-SHA512: b7eeda54f8db900f077417c0431f659c67e686e2fc078f8c713e37ed75b8bc862814ce20e8400741638e35e224d7284ad16172bf5f82168f803376d0c9ec4524
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions