On Fri, Sep 01, 2017 at 03:09:34PM -0700, Frank Filz wrote:
> Lately, we have been plagued by a lot of intermittent test failures.
> 
> I have seen intermittent failures in pynfs WRT14, WRT15, and WRT16. These
> have not been resolved by the latest ntirpc pullup.
> 
> Additionally, we see a lot of intermittent failures in the continuous
> integration.
> 
> A big issue with the Centos CI is that it seems to have a fragile setup, and
> sometimes doesn't even succeed in trying to build Ganesha, and then fires a
> Verified -1. This makes it hard to evaluate what patches are actually ready
> for integration.

We can look into this, but it helps if you can provide a link to the
patch in GerritHub or the job in the CI.

> An additional issue with the Centos CI is that the failure logs often aren't
> preserved long enough to even diagnose the issue.

That is something we can change. Some jobs do not delete the results,
but others seem to do. How long (in days), or how many results would you
like to keep?

> The result is that honestly, I mostly ignore the Centos CI results. They
> almost might as well not be run...

This is definitely not what we want, so lets fix the problems.

... snip!

> Let's talk about CI more on a near time concall (it would help if Niels and
> Jiffin could join a call to talk about this, our next call might be too soon
> for that).

Tuesdays tend to be very busy for me, and I am not sure I can join the
call next week. Arthy did some work on the jobs in the CentOS CI, she
could probably work with Jiffin to make any changes that improve the
experience for you. I'm happy to help out where I can too, of course :-)

Thanks,
Niels

------------------------------------------------------------------------------
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

Reply via email to