Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[qa] pull-tester: Run rpc test in parallel #7972
@MarcoFalke This is great, thanks for tackling! Any idea what's causing the travis failure?
I think it would be nice to make the number of simultaneous jobs configurable on the command line; the default of 4 seems good but being able to tweak it for the machine it's running on (say if other developers run this script locally, as I do) would be nice.
I also noticed that by re-sorting the standard tests so that the slowest jobs start first, I was able to get the runtime of all the standard tests running in parallel down to the same as running the single longest test (
Hm, I just ran the extended tests and got an odd failure -- this test looks like it is supposed to be marked successful.
Maybe that last line about "unable to flush" is going to stderr, causing this to be recorded as failure? If so then probably the test should be fixed.
This was referenced
May 6, 2016
referenced this pull request
May 9, 2016
Now I'm too lazzy to run them before this patch to compare...benchmark conclusion: this is great.
It also comes to mind that, in terms of time, only smartfees and pruning deserve to be in the extended tests group more then walletbackup. But probably moving walletbackup to the extended tests (and maybe some of the faster ones out of the extended group to the regular one at the same time?) is out of the scope of this PR.