<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 1 July 2016 at 09:59, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@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 class="HOEnZb"><div class="h5">On Thu, Jun 30, 2016 at 07:58:01PM +0530, M S Vishwanath Bhat wrote:<br>
> On 30 June 2016 at 14:59, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
><br>
> > On Thu, Jun 30, 2016 at 02:09:25PM +0530, Nigel Babu wrote:<br>
> ><br>
> > .. snip<br>
> ><br>
> > > > In order to make Gluster more stable, and prevent problems like this<br>
> > > > again, we really need to work on automating test cases. I hope all<br>
> > > > maintainers are thinking about how they want to test the components<br>
> > they<br>
> > > > are responsible for. For example, I'm planning to run the upstream QEMU<br>
> > > > tests against our nightly builds (libgfapi), and similar for the<br>
> > > > connectathon tests (Gluster/NFS). At one point it should be possible to<br>
> > > > wrap these in DiSTAF, but the DiSTAF job in the CentOS CI is not ready<br>
> > > > yet.<br>
> ><br>
> > .. snip<br>
> ><br>
> > > What needs to happen for DiSTAF job on Centos CI? I'm pushing hard to<br>
> > get more<br>
> > > DiSTAF tests upstream. I can help solve the pipeline/infra issues<br>
> > related to<br>
> > > this.<br>
> ><br>
> > The job is not functional yet, an attempt was made to add it:<br>
> ><br>
> > <a href="https://ci.centos.org/view/Gluster/job/gluster_nightly_distaf/" rel="noreferrer" target="_blank">https://ci.centos.org/view/Gluster/job/gluster_nightly_distaf/</a><br>
> ><br>
> > <a href="https://github.com/gluster/glusterfs-patch-acceptance-tests/tree/master/centos-ci/distaf_nightly" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-patch-acceptance-tests/tree/master/centos-ci/distaf_nightly</a><br>
> ><br>
> > I'm not sure what is blocking progress. Kaushal and MS (who recently<br>
> > switched to a different job) were planning to set it up.<br>
> ><br>
><br>
> TBH it wasn't made to run because there wasn't any tests there. There was<br>
> only one test which was very trivial, so there was not value add really.<br>
> But since we have more tests coming in now (over last weekend), we can try<br>
> and set it up now.<br>
><br>
> I am happy to continue from where I left off about the distaf Centos CI. I<br>
> will start working on this tomorrow evening through the weekend and update<br>
> you guys on Monday.<br>
><br>
> Also, to run distaf CentOS CI, we need to install gluster and setup the<br>
> backend xfs bricks (these two things are not taken care by distaf) before<br>
> starting the distaf run. I had thought making use of gdeploy for this<br>
> purpose. If you guys have any better solutions, please let me know.<br>
><br>
> PS: My ssh keys have changed, so I might need some help uploading the new<br>
> set of keys, If I can't find my old ssh keys.<br>
><br>
> Best Regards,<br>
> Vishwanath<br>
><br>
><br>
> HTH,<br>
> > Niels<br>
> ><br>
<br>
</div></div>Hi Vishwanath,<br>
<br>
Please make sure there's ample documentation about the entire process. It would<br>
be very helpful if you get the script into the patch acceptance tests repo[1].<br>
<br>
[1]: <a href="https://github.com/gluster/glusterfs-patch-acceptance-tests" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-patch-acceptance-tests</a></blockquote><div><br></div><div>The scripts are already part of the patch acceptance tests. But they aren't complete (integration with gdeploy pending). I will update them once I complete it and test it.</div><div><br></div><div>Best Regards,</div><div>Vishwanath</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
--<br>
nigelb<br>
</blockquote></div><br></div></div>