Bug 711584

Summary:	python tests failing on sparc
Product:	[Fedora] Fedora	Reporter:	Dennis Gilmore <dennis>
Component:	python	Assignee:	Dave Malcolm <dmalcolm>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	dan, dmalcolm, ivazqueznet, jonathansteffan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-07 16:09:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dennis Gilmore 2011-06-07 19:55:54 UTC

Description of problem:
3 tests are failing on sparc 
http://sparc.koji.fedoraproject.org/koji/taskinfo?taskID=112068

3 tests failed:
    test_ctypes test_openpty test_pty

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dave Malcolm 2011-06-07 20:03:30 UTC

Pasting the detailed errors inline here

test_ctypes:
======================================================================
ERROR: test_gl (ctypes.test.test_find.Test_OpenGL_libs)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.1/Lib/ctypes/test/test_find.py", line 34, in setUp
    self.gl = CDLL(lib_gl, mode=RTLD_GLOBAL)
  File "/builddir/build/BUILD/Python-2.7.1/Lib/ctypes/__init__.py", line 353, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /usr/lib/libGL.so.1: undefined symbol: security_get_boolean_active
======================================================================
FAIL: test_ulonglong (ctypes.test.test_callbacks.Callbacks)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.1/Lib/ctypes/test/test_callbacks.py", line 72, in test_ulonglong
    self.check_type(c_ulonglong, 10955412242170339782)
  File "/builddir/build/BUILD/Python-2.7.1/Lib/ctypes/test/test_callbacks.py", line 31, in check_type
    self.assertEqual(result, arg)
AssertionError: 10955412241121898851L != 10955412242170339782L
----------------------------------------------------------------------
Ran 331 tests in 6.293s
FAILED (failures=1, errors=1, skipped=1)

Comment 2 Dave Malcolm 2011-06-07 20:03:49 UTC

test_openpty:

test test_openpty failed -- Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.1/Lib/test/test_openpty.py", line 12, in test
    master, slave = os.openpty()
OSError: [Errno 2] No such file or directory
Re-running test 'test_openpty' in verbose mode
test (test.test_openpty.OpenptyTest) ... ERROR
======================================================================
ERROR: test (test.test_openpty.OpenptyTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.1/Lib/test/test_openpty.py", line 12, in test
    master, slave = os.openpty()
OSError: [Errno 2] No such file or directory
----------------------------------------------------------------------
Ran 1 test in 0.003s
FAILED (errors=1)

Comment 3 Dave Malcolm 2011-06-07 20:04:11 UTC

test_pty:

test test_pty failed -- Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.1/Lib/test/test_pty.py", line 114, in test_fork
    pid, master_fd = pty.fork()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 107, in fork
    master_fd, slave_fd = openpty()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 29, in openpty
    master_fd, slave_name = _open_terminal()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 70, in _open_terminal
    raise os.error, 'out of pty devices'
OSError: out of pty devices
Re-running test 'test_pty' in verbose mode
test_basic (test.test_pty.PtyTest) ... skipped 'Pseudo-terminals (seemingly) not functional.'
test_fork (test.test_pty.PtyTest) ... ERROR
======================================================================
ERROR: test_fork (test.test_pty.PtyTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.1/Lib/test/test_pty.py", line 114, in test_fork
    pid, master_fd = pty.fork()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 107, in fork
    master_fd, slave_fd = openpty()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 29, in openpty
    master_fd, slave_name = _open_terminal()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 70, in _open_terminal
    raise os.error, 'out of pty devices'
OSError: out of pty devices
----------------------------------------------------------------------
Ran 2 tests in 0.078s
FAILED (errors=1, skipped=1)
test test_pty failed -- Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.1/Lib/test/test_pty.py", line 114, in test_fork
    pid, master_fd = pty.fork()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 107, in fork
    master_fd, slave_fd = openpty()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 29, in openpty
    master_fd, slave_name = _open_terminal()
  File "/builddir/build/BUILD/Python-2.7.1/Lib/pty.py", line 70, in _open_terminal
    raise os.error, 'out of pty devices'
OSError: out of pty devices

Comment 4 Dan Horák 2011-06-20 10:58:52 UTC

The failing "pty" tests are likely caused by mock, see bug #714627

Dennis, what version of mock do you have on the sparc builders?

Comment 5 Dave Malcolm 2011-06-22 18:49:27 UTC

(In reply to comment #1)
> Pasting the detailed errors inline here
> 
> test_ctypes:
> ======================================================================
> ERROR: test_gl (ctypes.test.test_find.Test_OpenGL_libs)
> ----------------------------------------------------------------------

...snip...

> ======================================================================
> FAIL: test_ulonglong (ctypes.test.test_callbacks.Callbacks)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/builddir/build/BUILD/Python-2.7.1/Lib/ctypes/test/test_callbacks.py",
> line 72, in test_ulonglong
>     self.check_type(c_ulonglong, 10955412242170339782)
>   File "/builddir/build/BUILD/Python-2.7.1/Lib/ctypes/test/test_callbacks.py",
> line 31, in check_type
>     self.assertEqual(result, arg)
> AssertionError: 10955412241121898851L != 10955412242170339782L
> ----------------------------------------------------------------------
This one seems to be:
  http://bugs.python.org/issue8314
which seems to be a libffi bug.

Comment 6 Dave Malcolm 2011-06-22 18:50:17 UTC

(In reply to comment #5)
> This one seems to be:
>   http://bugs.python.org/issue8314
> which seems to be a libffi bug.
Note that in our build of Python we delete the python tarball's embedded copy of libffi in %prep and instead build against the system libffi.

Comment 7 Fedora End Of Life 2012-08-07 16:09:16 UTC

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping