[Gluster-Maintainers] [Gluster-devel] Master branch lock down status

Ravishankar N ravishankar at redhat.com
Wed Aug 8 08:30:12 UTC 2018

On 08/08/2018 05:07 AM, Shyam Ranganathan wrote:
> 5) Current test failures
> We still have the following tests failing and some without any RCA or
> attention, (If something is incorrect, write back).
> ./tests/basic/afr/add-brick-self-heal.t (needs attention)
 From the runs captured at https://review.gluster.org/#/c/20637/ , I saw 
that the latest runs where this particular .t failed were at 
https://build.gluster.org/job/line-coverage/415 and 
In both of these runs, there are no gluster 'regression' logs available 
at https://build.gluster.org/job/line-coverage/<build-number>/artifact. 
I have raised BZ 1613721 for it.

Also, Shyam was saying that in case of retries, the old (failure) logs 
get overwritten by the retries which are successful. Can we disable 
re-trying the .ts when they fail just for this lock down period alone so 
that we do have the logs?


More information about the maintainers mailing list