[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-20 Thread Terry J. Reedy
Terry J. Reedy added the comment: Fixed twice in all 3 versions. Thanks for the heads-up. -- ___ Python tracker ___

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-20 Thread Martin Panter
Martin Panter added the comment: Terry, in revision 6c8dd4cb4ee7 you wrote “Fix warning tom test_config.” Perhaps this is meant to say “. . . from test_config_key” (taken from b10a312f6d00)? -- nosy: +martin.panter ___ Python tracker

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-20 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-20 Thread Roundup Robot
Roundup Robot added the comment: New changeset 1c4cb01723a0 by Terry Jan Reedy in branch '2.7': Issue #27714: Remove unneeded non-idempotent call that fails on retest. https://hg.python.org/cpython/rev/1c4cb01723a0 New changeset 0e4bea7c8c00 by Terry Jan Reedy in branch '3.5': Issue #27714:

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-17 Thread Ned Deily
Ned Deily added the comment: "Could you try the comment out test of macosx call for test_autocomplete (around line 30 to 35) in 2.7 and 3.5?" Commenting out the mac.setupApp call in the test setup class did not appear to affect the running of the tests for either 2.7 or 3.5. --

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-16 Thread Terry J. Reedy
Terry J. Reedy added the comment: I fixed #27611. Could you try the comment out test of macosx call for test_autocomplete (around line 30 to 35) in 2.7 and 3.5? If those also pass, I will patch all three and close this. -- ___ Python tracker

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-15 Thread Ned Deily
Ned Deily added the comment: "Ned, test_tix failing on some systems [...]" Sorry, Terry! I had forgotten about Issue27611 and didn't do a proper search. -- ___ Python tracker

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-15 Thread Terry J. Reedy
Terry J. Reedy added the comment: Ned, test_tix failing on some systems (but not Windows) after test_idle, because test_idle calls tk.NoDefaultRoot() (added June 21 in #24137) is #27611. Serhiy says there is a bug in tix, but no one has fix that yet. Zach says I should restore tkinter

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-15 Thread Ned Deily
Ned Deily added the comment: I just noticed another similar test dependency, this time between test_idle and test_tix. If run with -j set, the problem is not seen. This is still present in 3.6.0a4: $ python3.6 -m test -uall -w test_idle test_tix Run tests sequentially 0:00:00 [1/2]

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-12 Thread Ned Deily
Ned Deily added the comment: >So what happens if you comment out line 34? > macosx.setupApp(cls.root, None) That seems to eliminate the intermittent "IndexError: list assignment index out of range" and doesn't seem to cause any new errors. -- ___

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Terry J. Reedy
Terry J. Reedy added the comment: The issue with test_textview in 3.x is that tearDownModule deleted a module attribute, 'TV', that was not created in setUpModule. For 2.7, 'TV' is a class attribute that is created in setUpClass and deleted in tearDownClass, so it does not have the same

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Roundup Robot
Roundup Robot added the comment: New changeset 0de509a79181 by Terry Jan Reedy in branch '2.7': Issue #27714: For IDLE's test_textview, backport 3.x subclass with mocks https://hg.python.org/cpython/rev/0de509a79181 -- ___ Python tracker

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Terry J. Reedy
Terry J. Reedy added the comment: I agree. The issue may come up with other tests in the future. I just decided to do the part I knew how to do first ;-). For #18409, I added the mac call to Phil's original patch with the vague comment "now needed to run without raising". But it is not

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Roundup Robot
Roundup Robot added the comment: New changeset dc31fa499359 by Terry Jan Reedy in branch '3.5': Issue #27714: text_textview now passes when re-run in the same process https://hg.python.org/cpython/rev/dc31fa499359 -- ___ Python tracker

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Ned Deily
Ned Deily added the comment: Terry, b10a312f6d00 appears to fix most of the issue, that is, if I insert a deliberate failure into another IDLE test and use -w without -j, the four repeatable errors I identified above no longer occur. Thanks. However, the fifth, timing-dependent error still

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Roundup Robot
Roundup Robot added the comment: New changeset b10a312f6d00 by Terry Jan Reedy in branch 'default': Issue #27714: text_textview now passes when re-run in the same process https://hg.python.org/cpython/rev/b10a312f6d00 -- nosy: +python-dev ___ Python

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Terry J. Reedy
Terry J. Reedy added the comment: For test_textview, I triggered the symptom -- 4 'TV' NameErrors on re-run, by (temporarily) adding 1/0 to tearDownModule and running with -w. After removing the TV deletion, only the ZeroDivisionError remained. This experiment also resulted in a '''can't

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-10 Thread Terry J. Reedy
Terry J. Reedy added the comment: Mark, the 'question above' was actually posted to #27380, the original query issue. -- ___ Python tracker ___

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-09 Thread Terry J. Reedy
Terry J. Reedy added the comment: Mark, the 'question above' was actually posted to #27380, the original query issue. -- ___ Python tracker ___

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-09 Thread Terry J. Reedy
Terry J. Reedy added the comment: Mark, see questions about Mac above. Basically, do we still need to add 'file://'? The test_textview repeat errors are eliminated by removing 'del TV' in tearDownModule. I added it in what seems to be an excess of caution when chasing down tk warnings

[issue27714] some test_idle tests are not re-runnable, producing false failures with regrtest -w option

2016-08-08 Thread Ned Deily
New submission from Ned Deily: If you run test_idle using the standard Python regression test runner, regrtest, and use regrtest's -w option (to re-run failure test verbosely) *without* using regrtest's -j option (to run tests in separate processes), any real test failure triggering a rerun