Re: [Gluster-devel] [Feature request]: Regression to take more patches in single instance

[Jeff Darcy]

On 07/31/2013 07:35 AM, Amar Tumballi wrote:
> I was trying to fire some regression builds on very minor patches today, and
>  noticed (always known, but faced pain of 'waiting' today) that we can fire
>  regression build on only one patch (or a patchset if its submitted with
> dependency added while submitting). And each regression run takes approx
> 30mins.
>
> With this model, we can at max take only ~45 patches in a day, which won't
> scale up if we want to grow with more people participating in code
> contribution. Would be great to have an option to submit regression run with
>  multiple patch numbers, (technically they should be applicable one top of
> other in any order if not dependent), and it should work fine. That way, we
> can handle more review load in future.

Maybe my brain has been baked too much by the sun, but I thought I'd seen cases
where a regression run on a patch with dependencies automatically validated
everything in the stack.  Not so?  That still places a burden on patch
submitters to make sure dependencies are specified (shouldn't be a problem
since the current tendency is to *over*specify dependencies) and on the person
starting the run to pick the top of the stack, but it does allow us to kill
multiple birds with one stone.

As for scaling, isn't the basic solution to add more worker machines?  That
would multiply the daily throughput by the number of workers, and decrease
latency for simultaneously submitted runs proportionally.