Python 3.5 is approved for Fedora 24[1], which is scheduled to ship in
May[2]
We have several places in the source where Python 2 is an explicit
requirement.
Do we want to rethink the hard requirement for Python 2? I suspect we
should.
[1]https://fedoraproject.org/wiki/Releases/24/ChangeSet
Hi all
I have the followif changes awaiting code review/merge:
http://review.gluster.org/13204
http://review.gluster.org/13205
http://review.gluster.org/13245
http://review.gluster.org/13247
--
Emmanuel Dreyfus
m...@netbsd.org
___
Gluster-devel
XFS. Server side works OK, I'm able to mount volume again. Brick is 30% full.
On понеділок, 18 січня 2016 р. 15:07:18 EET baul jianguo wrote:
> What is your brick file system? and the glusterfsd process and all
> thread status?
> I met same issue when client app such as rsync stay in D status,and
On Sat, Jan 16, 2016 at 2:25 AM, Vijay Bellur wrote:
> On 01/15/2016 08:38 AM, Soumya Koduri wrote:
>
>>
>>
>>
>> On 01/15/2016 06:52 PM, Soumya Koduri wrote:
>>
>>>
>>>
>>> On 01/14/2016 08:41 PM, Vijay Bellur wrote:
>>>
On 01/14/2016 04:11 AM, Jiffin Tony Thottan
Hi,
I have a simple gluster volume made up of 2 bricks using
distribute (running on the FreeBSD port of 3.7.6).
When I do a "rm -rf " for a fairly large tree, I
sometimes get "Directory not empty" errors.
When I look in the directory (even after an unmount, shutdown,
restart, remount) the "ls -l"
On 01/18/2016 06:18 PM, Rick Macklem wrote:
Hi,
I have a simple gluster volume made up of 2 bricks using
distribute (running on the FreeBSD port of 3.7.6).
When I do a "rm -rf " for a fairly large tree, I
sometimes get "Directory not empty" errors.
When I look in the directory (even after an
https://build.gluster.org/job/glusterfs-devrpms-el7/6734/console
--
Error Summary
-
Disk Requirements:
At least 104MB more space needed on the / filesystem.
+ exit 1
Build step 'Execute shell' marked build as failure
We're kicking off an updated Monthly Newsletter, coming out mid-month.
We'll highlight special posts, news and noteworthy threads from the
mailing lists, events, and other things that are important for the
Gluster community.
== Community Survey Followup ==
Hi
Spurious regression failures make developers frustrated. One submits a
change and gets completely unrelated failures. The only way out is to
retrigger regression until it passes, a boring and time-wasting task.
Sometimes after 4 or 5 failed runs, the submitter realize there is a
real issue and
- Original Message -
> From: "Rick Macklem"
> To: "Gluster Devel"
> Sent: Tuesday, January 19, 2016 4:48:21 AM
> Subject: [Gluster-devel] rm -r problem on FreeBSD port
>
> Hi,
>
> I have a simple gluster volume made up of 2 bricks
Hi Saravna,
./tests/bugs/changelog/bug-1208470.t seems to have failed a NetBSD run:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/17651/consoleFull
Not sure if it is spurious as it passed in the subsequent run. Please
have a look.
Thanks,
Ravi
Hi Rick,
Could you get us some more information about your setup:
1) Are you parallely doing 'rm -r' from multiple mount points? Or are you doing
'ls' while rm was in progress?
2) Is the error just a one time occurrence or do you still see it when you try
and remove the directory?
3) The
Ravishankar N wrote:
Hi Saravna,
./tests/bugs/changelog/bug-1208470.t seems to have failed a NetBSD run:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/17651/consoleFull
Not sure if it is spurious as it passed in the subsequent run. Please
have a look.
Might be too soon to
Python 2 and 3 can co exists. If Python 3 used by default, then we may
have to change the script heading from `#!/usr/bin/python` to
`#!/usr/bin/env python2`.
We need to modify the code where python command is used to call python
script.
For example, `PYTHON GSYNCD` to `PYTHON2 GSYNCD`
Hi,
Changing our code to make use of Python's "six" module will help maintain code
that will run both on Python 2 and Python 3.
https://pypi.python.org/pypi/six
Regards,
-Prashanth Pai
- Original Message -
> From: "Aravinda"
> To: "Kaleb S. KEITHLEY"
Hi Ravi,
I can run this locally, seems like spurious.
Let me know if you see again.
Please correct my email id, you are addressing another Saravana :)
Thanks,
Saravana
On 01/19/2016 09:42 AM, Venky Shankar wrote:
Ravishankar N wrote:
Hi Saravna,
./tests/bugs/changelog/bug-1208470.t seems
On 01/19/2016 12:01 PM, Venky Shankar wrote:
Saravanakumar Arumugam wrote:
Hi Ravi,
I can run this locally, seems like spurious.
Works fine on Linux for me too.Maybe its observed easily on BSD.
Let me know if you see again.
To be safe, it would benefit to have sleep(1) before the check.
Hi,
Yes, I can easily add additional 2 second sleep.
But, the problem here is: irrespective of anything(especially these
timing changes), it should not create any additional changelog.
It is a test volume created for test purpose where no I/O is carried out.
So, we may end up putting band-aid
- Original Message -
> From: "Rick Macklem"
> To: "Raghavendra Gowdappa"
> Cc: "Jeff Darcy" , "Raghavendra G"
> , "freebsd-fs"
> , "Hubbard Jordan" ,
Saravanakumar Arumugam wrote:
Hi Ravi,
I can run this locally, seems like spurious.
Let me know if you see again.
To be safe, it would benefit to have sleep(1) before the check.
Please correct my email id, you are addressing another Saravana :)
Thanks,
Saravana
On 01/19/2016 09:42 AM,
Raghavendra Gowdappa wrote:
>
>
> - Original Message -
> > From: "Rick Macklem"
> > To: "Jeff Darcy"
> > Cc: "Raghavendra G" , "freebsd-fs"
> > , "Hubbard Jordan"
> > , "Xavier
21 matches
Mail list logo