[issue8281] test_gdb_sample fails

2010-04-17 Thread STINNER Victor
STINNER Victor added the comment: Oops, my last message (msg103435) was for #8434, not this issue. Anyway, #8434 is a duplicate of #8279, it doesn't matter. -- ___ Python tracker __

[issue8281] test_gdb_sample fails

2010-04-17 Thread STINNER Victor
STINNER Victor added the comment: test_gdb.py refers to test_gdb_sample.py instead of gdb_sample.py. Attached patch fixes that. But then I get new errors: --- ... Verify the pretty-printing of unicode values ... ok test_basic_command (__main__.PyListTests)

[issue8281] test_gdb_sample fails

2010-04-01 Thread Antoine Pitrou
Antoine Pitrou added the comment: > (Note that due to issue 8279 the file isn't actually used at the moment > by test_gdb.py so it should be safe to rename. I have a patch attached > to that latter bug; I'll fix up the patch after that file is renamed). Thank you, this is done in r79557. --

[issue8281] test_gdb_sample fails

2010-04-01 Thread Dave Malcolm
Dave Malcolm added the comment: "gdb_sample.py" as a name works for me. I don't have commit rights to SVN so I can't perform the rename myself. (Note that due to issue 8279 the file isn't actually used at the moment by test_gdb.py so it should be safe to rename. I have a patch attached to t

[issue8281] test_gdb_sample fails

2010-04-01 Thread Antoine Pitrou
Antoine Pitrou added the comment: > I would probably be simplest to rename it so it doesn't have a "test_" prefix. Indeed. Otherwise it gets caught and executed by regrtest as part of the standard test suite. > How about "sample_for_test_gdb.py", or somesuch? Shorter would be better :) For ex

[issue8281] test_gdb_sample fails

2010-04-01 Thread Florent Xicluna
Changes by Florent Xicluna : -- keywords: +buildbot priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue8281] test_gdb_sample fails

2010-04-01 Thread Dave Malcolm
Dave Malcolm added the comment: Sorry about that. "test_gdb_sample.py" is merely a sample script for use by "test_gdb.py" (see issue 8032); it's not intended to do anything useful by itself (though it does need a "print" invocation, since test_gdb.py uses a breakpoint in PyObject_Print). I

[issue8281] test_gdb_sample fails

2010-04-01 Thread Antoine Pitrou
New submission from Antoine Pitrou : This doesn't happen in verbose mode, because stdout isn't checked: $ ./python -m test.regrtest test_gdb_sample test_gdb_sample test test_gdb_sample produced unexpected output: ** 42 ***