Re: Master branch lock down status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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 https://build.gluster.org/job/line-coverage/421/. 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?

Regards,
Ravi

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux