Can we check the following failure?
1 test(s) failed
./tests/00-geo-rep/georep-basic-dr-rsync-arbiter.t
-- Forwarded message -
From:
Date: Mon, Jul 1, 2019 at 11:48 PM
Subject: [Gluster-Maintainers] Build failed in Jenkins:
regression-test-burn-in #4631
To:
See <
Can we check these failures please?
2 test(s) failed
./tests/bugs/glusterd/bug-1699339.t
./tests/bugs/glusterd/bug-857330/normal.t
-- Forwarded message -
From:
Date: Wed, Jul 3, 2019 at 12:08 AM
Subject: [Gluster-Maintainers] Build failed in Jenkins:
regression-test-burn-in
Hi Team,
Release 7 branch has been created in upstream.
## Schedule
Curretnly the plan working backwards on the schedule, here's what we have:
- Announcement: Week of Aug 4th, 2019
- GA tagging: Aug-02-2019
- RC1: On demand before GA
- RC0: July-03-2019
- Late features cut-off: Week of
On 02/07/19 8:52 PM, FNU Raghavendra Manjunath wrote:
Hi All,
In glusterfs, there is an issue regarding the fallocate behavior. In
short, if someone does fallocate from the mount point with some size
that is greater than the available size in the backend filesystem
where the file is
Hi All,
In glusterfs, there is an issue regarding the fallocate behavior. In short,
if someone does fallocate from the mount point with some size that is
greater than the available size in the backend filesystem where the file is
present, then fallocate can fail with a subset of the required
