[SSSD] [RFC] Add basic support for CI test execution

Pavel Reichl preichl at redhat.com
Wed Jun 11 14:54:38 UTC 2014


On Wed, 2014-06-11 at 17:28 +0300, Nikolai Kondrashov wrote:
> 
> >> Sure, there are various ways to make Valgrind happy, although none of them are
> >> very easy. The important thing is that we would have a way to track it now.
> >> This way, or another we should arrive to zero Valgrind errors.
> >>
> > Ignoring is not a good way for CI. We need to find a viable solution.
> 
> I agree and I'm not saying we should ignore it always. This ignoring is to
> enable CI earlier, so we can get at least *some* tests to run. And having CI
> running these tests (even though they're ignored) will make fixing the
> failures easier, than without the CI. If only for the ability to trigger
> background runs on various distros at once. Once we have the issues fixed we
> will enforce the check.
> 

Is it viable option to somehow "store" current problems found by
valgrind/clang/other tools and just report the new ones? 

Doing so would allow us to use all benefits of this tools without need
to promptly fix issues created over years and we could use this approach
to mask false positives.








More information about the sssd-devel mailing list