<div dir="ltr">One thing we could do with some tests I know is to remove some of them.<div><br></div><div>EC currently runs the same test on multiple volume configurations (2+1, 3+1, 4+1, 3+2, 4+2, 4+3 and 8+4). I think we could reduce it to two common configurations (2+1 and 4+2) and one or two special configurations (3+1 and/or 3+2). This will remove the biggest ones, that take most of the time, while keeping the basic things still tested.</div><div><br></div><div>Xavi</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 3 November 2017 at 17:50, Amar Tumballi <span dir="ltr"><<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">All,<div><br></div><div>While we discussed many other things, we also discussed about reducing time taken for the regression jobs. As it stands now, it take around 5hr 40mins to complete a single run.</div><div><br></div><div>There were many suggestions:</div><div><br></div><div><ul><li>Run them in parallel (as each .t test is independent of each other)</li><li>Revisit the tests taking long time (20 tests take almost 6000 seconds as of now).</li><li>See if we can run the tests in docker (but the issue is the machines we have are of 2cores, so there may not be much gain)</li></ul><div><br></div></div><div>There are other suggestions as well:</div><div><br></div><div><ul><li>Spend effort and see if there are repeated steps, and merge the tests.</li><ul><li>Most of the time is spent in starting the processes and cleaning up.</li><li>Most of the tests run the similar volume create command (depending on the volume type), and run few different type of I/O in different tests.</li><li>Try to see if these things can be merged.</li><li>Most of the bug-fix .t files belong to this category too.</li></ul><li>Classify the tests specific to few non-overlapping volume types and depending on the changeset in the patch (based on the files changed) decide which are the groups to run. </li><ul><li>For example, you can't have replicate and disperse volume type together.</li></ul></ul><div><br></div></div><div>---- </div><div><br></div><div>More ideas and suggestions welcome.</div><div><br></div><div><br></div><div>Regards,</div><div>Amar</div><div><div><br></div>
</div></div>
<br>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br></blockquote></div><br></div>