Re: Release 3.11: Backports needed and regression failure status

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

 





On 23 May 2017 at 06:56, Shyam <srangana@xxxxxxxxxx> wrote:
Hi,

Backport status:
The following patches are available in release-3.10 but not in release-3.11,
    - https://review.gluster.org/#/c/17197/ (@nithya request the backport)

Apologies. Patch available at https://review.gluster.org/17373
 
    - https://review.gluster.org/#/c/17175/ (@hari request the backport)

Test case status (from fstat):

Following test case was marked bad in master, but not in 3.11 and has caused a few aborted runs, I have backported the change, so we should be good in the future,
  - tests/features/lock_revocation.t (backport: https://review.gluster.org/#/c/17360/ )

Request that any test case when marked bad in master, be looked at for the prior release (in this case 3.11) so that spurious regression failures are avoided in that branch as well.

Following test cases failed 1 time in the last 3 weeks, so nothing critical, but reporting it here nevertheless,
- ./tests/basic/afr/add-brick-self-heal.t
- ./tests/basic/tier/legacy-many.t
- ./tests/bugs/glusterd/bug-1345727-bricks-stop-on-no-quorum-validation.t

Thanks,
Shyam


_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://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