:[email protected]> >
> *Cc:* [email protected]
> <mailto:[email protected]>
> *Subject:* Re: [Nfs-ganesha-devel] Conditional compile failures
>
>
>
> If we make those as some kind of cmake build configs, then deve
ts issuing Verify-1. If there’s a build option set someone thinks
> > might be relevant that we don’t succeed in compiling for, we need to fix
> > it immediately.
> >
> >
> >
> > Frank
> >
> >
> >
> > *From:*Malahal Naineni [mailto:[email protected]
Sent:* Monday, May 8, 2017 9:01 AM
> *To:* Frank Filz
> *Cc:* [email protected]
> *Subject:* Re: [Nfs-ganesha-devel] Conditional compile failures
>
>
>
> If we make those as some kind of cmake build configs, then developers
> can also build those combinati
Filz
Cc: [email protected]
Subject: Re: [Nfs-ganesha-devel] Conditional compile failures
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
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
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
