[issue24215] test_trace uses test_pprint

Serhiy Storchaka added the comment: There is different failure when run this test separately: $ ./python -m test -v -m test_coverage test_trace ... == FAIL: test_coverage (test.test_trace.TestCoverage)

[issue24215] test_trace uses test_pprint

Roundup Robot added the comment: New changeset 2c074a8dd084 by Serhiy Storchaka in branch '3.4': Issue 24215: Added tests for more builtin types in test_pprint. https://hg.python.org/cpython/rev/2c074a8dd084 New changeset da711bdcc1bf by Serhiy Storchaka in branch 'default': Issue 24215: Added t

[issue24215] test_trace uses test_pprint

Terry J. Reedy added the comment: My recipe worked for me, but I am not surprised that it might fail elsewhere. Is the specific purpose of the two problemmatic test_trace test to test that trace works with unittest? It did not seem like it to me. If not, test_trace could be decoupled from

[issue24215] test_trace uses test_pprint

Serhiy Storchaka added the comment: There are issues with additional tests for uu. The fact that test_trace fails with the -m option means that any file that runs unittest is not good example (unittest looks on sys.argv). -- ___ Python tracker

[issue24215] test_trace uses test_pprint

R. David Murray added the comment: If you are looking for a small test file to switch to, perhaps test_uu would be a good candidate. It isn't very likely to grow, since I don't think uu encoding is used much any more, so the likelyhood of someone caring about it is relatively low. But I have

[issue24215] test_trace uses test_pprint

Serhiy Storchaka added the comment: Sorry, I expected this issue be solved much faster. Unfortunately Terry's recipe doesn't work. Here is a patch that reapplies changes that broke buildbots (additional tests for buildins and making test_pprint discoverable), and also fixes test_trace and make

[issue24215] test_trace uses test_pprint

Changes by R. David Murray : -- priority: release blocker -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue24215] test_trace uses test_pprint

Roundup Robot added the comment: New changeset cf52756f19b6 by R David Murray in branch '3.4': #24215: also back out changeset that broke test_trace in 3.4. https://hg.python.org/cpython/rev/cf52756f19b6 -- nosy: +python-dev ___ Python tracker

[issue24215] test_trace uses test_pprint

R. David Murray added the comment: I've backed out the change set that broke the buildbots (see de9c43fabda6). I can understand this changeset getting committed, since one doesn't normally expect a change in the tests to break other tests (though I myself do often run the full test suite anywa

[issue24215] test_trace uses test_pprint

Terry J. Reedy added the comment: Since test files should no longer have test_main, test_trace should no longer look for one. (And indeed, test_trace itself should be converted, which looks trivial.) The offending line is cmd='from test import test_pprint; test_pprint.test_main()'): The use

[issue24215] test_trace uses test_pprint

New submission from Serhiy Storchaka: Converting test_pprint to be unittest discoverable had broke the test_trace that uses test_main from test_pprint. == ERROR: test_coverage (test.test_trace.TestCoverage)