[issue13699] test_gdb has recently started failing
STINNER Victor
report at bugs.python.org
Wed Jan 4 04:37:27 CET 2012
STINNER Victor <victor.stinner at haypocalc.com> added the comment:
"test_gdb has started failing recently on my Ubuntu Natty system:
...
>>> sysconfig.get_config_vars()['PY_CFLAGS']
'-Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes'
...
Marking haypo as nosy since it might be related to recent changes for #13628."
Before my last change for #13628, test_gdb was skipped completly when Python was compiled in release mode (with gcc optimization, which is the default).
Except if you have an idea to improve python-gdb.py to make it find the frame pointer, the simple fix is to skip the failing tests if Python is optimized. I already add some @unittest.skipIf(python_is_optimized(), "Python was compiled with optimizations") in my commit 0b03cb97dac0.
Would you like to write such patch?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13699>
_______________________________________
More information about the Python-bugs-list
mailing list