[Gluster-devel] Change in test file, run only that test in regression job?

Nigel Babu nigelb at redhat.com
Fri Sep 8 11:12:21 UTC 2017


Hey, so I ended up implementing this slightly differently.

Please take a look: https://review.gluster.org/#/c/18213/

On Tue, Jul 11, 2017 at 2:27 PM, Raghavendra Talur <rtalur at redhat.com>
wrote:

> On Tue, Jul 11, 2017 at 1:51 PM, Atin Mukherjee <amukherj at redhat.com>
> wrote:
> > If a patch is all about .t changes, running the whole regression suite
> > instead of running those particular tests is not worth. This idea came up
> > while Nithya, Nigel & I were having conversations  around how to fix
> > regression failures faster if the change is only required at the test
> file.
> >
> > Does everyone in favour of this idea? If yes, can this be implemented
> Nigel?
>
> +1
> Jeff Darcy has implemented[1] ability to run only updated/added tests.
> We just have to invoke run-tests.sh with -H option.
>
> This does not determine if only tests have been added. It just makes
> sure we exit after running updated/added tests and don't run other
> tests.
> Nigel, you will have to check for "test only change* in jenkins and
> conditionally call run-tests.sh with -H
>
>
> [1] https://review.gluster.org/#/c/13439/
>
> Raghavendra Talur
>
>
> >
> > ~Atin
> >
> >
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
nigelb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170908/cee7c31a/attachment-0001.html>


More information about the Gluster-devel mailing list