[issue17835] test_io broken on PPC64 Linux

[James Spurin]

James Spurin added the comment:

With both the kernel parameters defined and undefined, I get the following 
output -

# /local/0/opt/python-3.4.1/bin/python
Python 3.4.1 (default, Sep 29 2014, 13:31:39)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux
Type help, copyright, credits or license for more information.
 from socket import socket, SO_SNDBUF, SOL_SOCKET
 s = socket()
 s.getsockopt(SOL_SOCKET, SO_SNDBUF)
16384

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17835
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17835] test_io broken on PPC64 Linux

[James Spurin]

James Spurin added the comment:

fcntl doesnt seem to like the parameter you mentioned -

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.5 (Santiago)
# /local/0/opt/python-3.4.1/bin/python
Python 3.4.1 (default, Sep 24 2014, 12:23:21)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux
Type help, copyright, credits or license for more information.
 import fcntl, os
 r, w = os.pipe()
 fcntl.fcntl(w, 1032)
Traceback (most recent call last):
  File stdin, line 1, in module
OSError: [Errno 22] Invalid argument


--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17835
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17835] test_io broken on PPC64 Linux

[James Spurin]

James Spurin added the comment:

I encountered similar issues to those discussed in this issue whilst compiling 
3.4.1 on 'Red Hat Enterprise Linux Server release 6.5 (Santiago)'

In particular, the following tests were failing -

[root@lonlx90800 ~]# /local/0/python-3.4.1/bin/python3 
/local/0/python-3.4.1/lib/python3.4/test/test_asyncio/test_subprocess.py
F...F...
==
FAIL: test_broken_pipe (__main__.SubprocessFastWatcherTests)
--
Traceback (most recent call last):
  File 
/local/0/python-3.4.1/lib/python3.4/test/test_asyncio/test_subprocess.py, 
line 129, in test_broken_pipe
self.loop.run_until_complete(proc.communicate(large_data))
AssertionError: BrokenPipeError not raised

==
FAIL: test_broken_pipe (__main__.SubprocessSafeWatcherTests)
--
Traceback (most recent call last):
  File 
/local/0/python-3.4.1/lib/python3.4/test/test_asyncio/test_subprocess.py, 
line 129, in test_broken_pipe
self.loop.run_until_complete(proc.communicate(large_data))
AssertionError: BrokenPipeError not raised

In this case, the issues are being caused by the following kernel parameters 
that we have for our default build -

#
## TIBCO network tuning #
#
net.core.rmem_default = 33554432
net.core.wmem_default = 33554432
net.core.rmem_max = 33554432
net.core.wmem_max = 33554432

Toggling the support.PIPE_MAX_SIZE to +32MB or temporarily removing these 
parameters mitigates the issue.  Is there a better way of calculating 
support.PIPE_MAX_SIZE so it is reflective of the actual OS value?

--
nosy: +spurin

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17835
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com