<div dir="ltr">So we have a job that's unmaintained and unwatched. If nobody steps up to own it in the next 2 weeks, I'll be deleting this job.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 14, 2018 at 4:49 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Feb 14, 2018 at 11:15:23AM +0530, Nigel Babu wrote:<br>
> Hello,<br>
><br>
> Centos CI has a run-tests-in-vagrant job. Do we continue to need this<br>
> anymore? It still runs master and 3.8. I don't see this job adding much<br>
> value at this point given we only look at results that are on<br>
> <a href="http://build.gluster.org" rel="noreferrer" target="_blank">build.gluster.org</a>. I'd like to use the extra capacity for other tests that<br>
> will run on centos-ci.<br>
<br>
</span>The ./run-tests-in-vagrant.sh script is ideally what developers run<br>
before submitting their patches. In case it fails, we should fix it.<br>
Being able to run tests locally is something many of the new<br>
contributors want to do. Having a controlled setup for the testing can<br>
really help with getting new contributors onboard.<br>
<br>
Hmm, and the script/job definitely seems to be broken with at least two<br>
parts:<br>
- the Vagrant version on CentOS uses the old URL to get the box<br>
- 00-georep-verify-setup.t fails, but the result is marked as SUCCESS<br>
<br>
It seems we need to get better at watching the CI, or at least be able<br>
to receive and handle notifications...<br>
<br>
Thanks,<br>
Niels<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div>