diff options
| author | laanwj <126646+laanwj@users.noreply.github.com> | 2022-01-05 17:19:47 +0100 |
|---|---|---|
| committer | laanwj <126646+laanwj@users.noreply.github.com> | 2022-01-05 17:19:54 +0100 |
| commit | 121d47afe3e67ff7f94d26e08a39573dccf652aa (patch) | |
| tree | 4a0a01c5f1f61fba45201be7f2c51748d8448ad6 /REVIEWERS | |
| parent | af7fba3af788e91a460582351d40f8f5e2118760 (diff) | |
| parent | 975097f424541a149c5b4e03816208aa76aad6b9 (diff) | |
| download | bitcoin-121d47afe3e67ff7f94d26e08a39573dccf652aa.tar.xz | |
Merge bitcoin/bitcoin#23799: test: Let test_runner.py start multiple jobs per timeslot
975097f424541a149c5b4e03816208aa76aad6b9 Let test_runner.py start multiple jobs per timeslot (Pieter Wuille)
Pull request description:
test_runner.py currently only checks every 0.5s whether any job has finished, and if so, starts at most one new job. At higher parallellism it becomes increasingly likely that multiple jobs have finished at the same time. Fix this by always noticing *all* finished jobs every timeslot, and starting as many new ones.
ACKs for top commit:
laanwj:
Code review and lightly tested ACK 975097f424541a149c5b4e03816208aa76aad6b9
prayank23:
ACK https://github.com/bitcoin/bitcoin/pull/23799/commits/975097f424541a149c5b4e03816208aa76aad6b9
Tree-SHA512: b70c51f05efcde9bc25475c192b86e86b4c399495b42dee20576af3e6b99e8298be8b9e82146abdabbaedb24a13ee158a7c8947518b16fc4f33a3b434935b550
Diffstat (limited to 'REVIEWERS')
0 files changed, 0 insertions, 0 deletions