This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: 2.5.1 latest svn fails test_curses and test_timeout
Type: behavior Stage: test needed
Components: Build, Tests Versions: Python 2.6
process
Status: closed Resolution: works for me
Dependencies: Superseder:
Assigned To: Nosy List: BreamoreBoy, akuchling, dfavor, nnorwitz, r.david.murray
Priority: normal Keywords:

Created on 2007-06-02 14:51 by dfavor, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (12)
msg32179 - (view) Author: David Favor (dfavor) Date: 2007-06-02 14:51
[root@net1 ~]# build_python
mkdir -p /build/work/Python-2.5.1
cd /build/work/Python-2.5.1
unset CDPATH
export TESTOPS='-l -u curses -u network -u urlfetch -u decimal -u compiler -u bsddb -u subprocess'
export CFLAGS='-pipe -fwrapv'
export MALLOC_CHECK_=0
make distclean
./configure --prefix=/usr/local/pkgs/python-2.5.1 --enable-shared --disable-static --disable-ipv6 
make
make testall
... ... ...
299 tests OK.
2 tests failed:
    test_curses test_timeout
20 tests skipped:
    test_aepack test_al test_applesingle test_bsddb185 test_cd test_cl
    test_gl test_imgfile test_macfs test_macostools test_nis
    test_pep277 test_plistlib test_scriptpackages test_startfile
    test_sunaudiodev test_unicode_file test_winreg test_winsound
    test_zipfile64
Those skips are all expected on linux2.
warning: DBTxn aborted in destructor.  No prior commit() or abort().
make: *** [testall] Error 1
exp=0, got ec=2, abort=1
msg32180 - (view) Author: David Favor (dfavor) Date: 2007-06-02 14:54
These fixes should also be dropped into the 2.6 tree.
msg32181 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2007-06-03 22:19
test_timeout often fails depending on if the system the test connects to is available or not (ie, the test sucks).  How does test_curses fail?  What platform?

BTW, you can use -u all.
msg32182 - (view) Author: David Favor (dfavor) Date: 2007-06-06 15:36
test test_timeout failed -- Traceback (most recent call last):
  File "/build/work/Python-2.5.1/Lib/test/test_timeout.py", line 128, in testConnectTimeout
    %(_delta, self.fuzz, _timeout))
AssertionError: timeout (8.00152) is more than 2 seconds more than expected (0.001) 
msg32183 - (view) Author: David Favor (dfavor) Date: 2007-06-06 15:37
test_curses
^[[?1049h^[[1;50r^[(B^[[m^[[4l^[[?7h^[[50;1H^[[?1049l^M^[[?1l^[>test test_curses crashed -- <class '_curses.error'>: endwin() returned ERR
msg32184 - (view) Author: David Favor (dfavor) Date: 2007-06-06 15:39
Latest 'svn up' shows both these tests still failing in both
the 2.5.1 and 2.6 trees.
msg32185 - (view) Author: David Favor (dfavor) Date: 2007-06-06 19:00
Answering platform request. Fedora 6 with latest patches.
msg32186 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2007-06-07 02:02
David, I don't have access to a fedora 6 box.  Could you either debug the problem or provide access to such a box?  I think I have seen the curses problem somewhere else, so this may be an API issue that the python module doesn't handle it correctly.
msg32187 - (view) Author: David Favor (dfavor) Date: 2007-06-07 18:20
The test_timeout problem appears solved in latest svn.

Neal, I'm new to Python. Let me know how to approach debugging this
and I'll let you know what happens.
msg59603 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2008-01-09 14:27
According to the man page for endwin() from ncurses, "In this
implementation endwin returns an error if the terminal was not
initialized." This doesn't make the problem any clearer to me.  Perhaps
the setupterm() or initscr() in Lib/tests/test_curses is failing in a
way that 
we aren't noticing.
msg116682 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2010-09-17 17:05
I can't believe that this is still relevant.
msg116684 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-09-17 17:17
The bug probably does still exist (see issue 7038 for a recent similar report).  However, without a repeatable test case we can't fix it, so leaving this closed is fine.  If the OP can still reproduce it we can try working on it again.
History
Date User Action Args
2022-04-11 14:56:24adminsetgithub: 45025
2010-09-17 17:17:49r.david.murraysetresolution: out of date -> works for me

messages: + msg116684
nosy: + r.david.murray
2010-09-17 17:05:54BreamoreBoysetstatus: open -> closed

nosy: + BreamoreBoy
messages: + msg116682

resolution: out of date
2009-05-12 17:36:03ajaksu2setversions: + Python 2.6, - Python 2.5
type: behavior
components: + Tests
stage: test needed
2008-01-09 14:27:00akuchlingsetnosy: + akuchling
messages: + msg59603
2007-06-02 14:51:36dfavorcreate