If we make those as some kind of cmake build configs, then developers can
also build those combinations before we push our code for review. Maybe,
have randconfig as well for developers to use but don't enforce in CI for
the time being (until it has some run time!)
Regards, malahal.
On Mon, May 8, 2017 at 9:19 PM, Frank Filz <ffilz...@mindspring.com> wrote:
> Every once in a while we get a report of a build failure from someone using
> build options other than what we normally build with.
>
> I'd like to propose that we pick some common combinations folks might like
> to build with and have those as part of one of our CI tests run on every
> patch since that is totally the type of thing that's easy to automate and a
> royal pain to test manually.
>
> Frank
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
