On Mon, Aug 13, 2018 at 02:32:19PM -0400, Shyam Ranganathan wrote:
> On 08/12/2018 08:42 PM, Shyam Ranganathan wrote:
> > As a means of keeping the focus going and squashing the remaining tests
> > that were failing sporadically, request each test/component owner to,
> >
> > - respond to this
On 08/12/2018 08:42 PM, Shyam Ranganathan wrote:
> As a means of keeping the focus going and squashing the remaining tests
> that were failing sporadically, request each test/component owner to,
>
> - respond to this mail changing the subject (testname.t) to the test
> name that they are
On 08/13/2018 02:32 PM, Shyam Ranganathan wrote:
> I will be adding a bug and a fix that tries this in a loop to avoid the
> potential race that I see above as the cause.
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1615582
Potential fix: https://review.gluster.org/c/glusterfs/+/20726
Shyam
On 08/12/2018 08:42 PM, Shyam Ranganathan wrote:
> As a means of keeping the focus going and squashing the remaining tests
> that were failing sporadically, request each test/component owner to,
>
> - respond to this mail changing the subject (testname.t) to the test
> name that they are
On 08/12/2018 08:42 PM, Shyam Ranganathan wrote:
> As a means of keeping the focus going and squashing the remaining tests
> that were failing sporadically, request each test/component owner to,
>
> - respond to this mail changing the subject (testname.t) to the test
> name that they are
On 08/13/2018 02:20 AM, Pranith Kumar Karampuri wrote:
> - At the end of 2 weeks, reassess master and nightly test status, and
> see if we need another drive towards stabilizing master by locking down
> the same and focusing only on test and code stability around the same.
>
>
> When
On 08/12/2018 08:42 PM, Shyam Ranganathan wrote:
> As a means of keeping the focus going and squashing the remaining tests
> that were failing sporadically, request each test/component owner to,
>
> - respond to this mail changing the subject (testname.t) to the test
> name that they are
On 08/12/2018 08:42 PM, Shyam Ranganathan wrote:
> As a means of keeping the focus going and squashing the remaining tests
> that were failing sporadically, request each test/component owner to,
>
> - respond to this mail changing the subject (testname.t) to the test
> name that they are
Hi,
I am working on Glusterfs v4.1.1 for Ubuntu 16.04 on big endian
architecture. After successful build and running the test cases, I
encountered a test case failure. The test case is:-
ยท ./tests/basic/namespace.t
In the test case ./tests/basic/namespace.t, a NAMESPACE_HASH is generated
On Mon, Aug 13, 2018 at 10:55 PM Shyam Ranganathan
wrote:
> On 08/13/2018 02:20 AM, Pranith Kumar Karampuri wrote:
> > - At the end of 2 weeks, reassess master and nightly test status, and
> > see if we need another drive towards stabilizing master by locking
> down
> > the same and
All,
I was consistently seeing failures for test
https://review.gluster.org/#/c/glusterfs/+/20639/12/tests/bugs/readdir-ahead/bug-1390050.t
TEST glusterfs --volfile-server=$H0 --volfile-id=$V0 $M0
rm -rf $M0/*
TEST mkdir -p $DIRECTORY
#rm -rf
$DIRECTORY/*
TEST touch $DIRECTORY/file{0..10}
On Mon, Aug 13, 2018 at 6:05 AM Shyam Ranganathan
wrote:
> Hi,
>
> So we have had master locked down for a week to ensure we only get fixes
> for failing tests in order to stabilize the code base, partly for
> release-5 branching as well.
>
> As of this weekend, we (Atin and myself) have been
Nigel,
Now that mater branch is reopened, can you please revoke the commit access
restrictions?
On Mon, 6 Aug 2018 at 09:12, Nigel Babu wrote:
> Hello folks,
>
> Master branch is now closed. Only a few people have commit access now and
> it's to be exclusively used to merge fixes to make
Oops, I apparently forgot to send out a note. Master has been since ~7 am
IST.
On Mon, Aug 13, 2018 at 4:25 PM Atin Mukherjee wrote:
> Nigel,
>
> Now that mater branch is reopened, can you please revoke the commit access
> restrictions?
>
> On Mon, 6 Aug 2018 at 09:12, Nigel Babu wrote:
>
>>
On 08/13/2018 06:12 AM, Shyam Ranganathan wrote:
As a means of keeping the focus going and squashing the remaining tests
that were failing sporadically, request each test/component owner to,
- respond to this mail changing the subject (testname.t) to the test
name that they are responding to
This is so nice. I tried it and succesfully created a test machine. It would be
great if there is a provision to extend the lifetime of vm's beyond the time
provided during creation. First I ran the ansible-playbook from the vm machine,
then I realized that has to be executed from outside
GlusterFS Coverity covscan results for the master branch are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-08-13-febee007/
Coverity covscan results for other active branches are also available at
This is great!
One thing that I'm noticing is that most proposed projects do not have
mentors at this time, which is pretty crucial to the success of these
projects.
Will signups close 20 August for that as well?
- amye
On Thu, Aug 9, 2018 at 11:16 PM Bhumika Goyal wrote:
> Hi all,
>
> *Gentle
18 matches
Mail list logo
