5.2/Lib/test/fork_wait.py", line 75, in
test_wait
self.wait_impl(cpid)
File "Lib/test/test_wait4.py", line 28, in wait_impl
self.assertEqual(spid, cpid)
AssertionError: 0 != 8417358
--end results--
Thanks for taking your time to respond. It is truly appreciated at
this end.
Kind regards,
-Randy Galbraith
--
http://mail.python.org/mailman/listinfo/python-list
.2/Lib/test/fork_wait.py", line 75, in test_wait
self.wait_impl(cpid)
File "Python-2.5.2/Lib/test/test_wait4.py", line 28, in wait_impl
self.assertEqual(spid, cpid)
AssertionError: 0 != 6840386
What do these failures indicate? Not sure of course, but will
research and report back
Thus it would seem use cif here resulted in a segment violation. I'll
continue to research this issue and report back to the group as I know
more. Perhaps solving the issue with the 'c' and 'm' libraries
(whatever they might be) will make the core dump go away. However,
for tonight, I'll need to stop here.
Kind regards,
-Randy Galbraith
--
http://mail.python.org/mailman/listinfo/python-list
-DPy_BUILD_CORE -o
Modules/python.o ./Modules/python.c
In file included from Include/Python.h:83,
from ./Modules/python.c:3:
Include/unicodeobject.h:73:2: error: #error Must define
Py_UNICODE_SIZE
What is Py_UNICODE_SIZE and why was it not defined? There are current
questions I have
more suitable?
(c) I am concerned about the two failing test cases: test_mmap and
test_wait4. Are there good reasons why these failures can be safely
ignored?
(d) Should I be concerned with the skips of test_largefile and
test_ctypes?
Much thanks in advance.
Kind regards,
-Randy Galbraith
