Message93557
Running regrtest over an installed, read-only Lib produces several test
failures, and regrtest crashes. In investigating these, which I will
deal with in other issues, I found that the regrtest runtest_inner
method takes a 'testdir' argument, and if it is none calls
'findtestdir'. findtestdir uses __file__ or arg[0] to compute the
directory in which regrtest is located, something that does not change
during the lifetime of a given regrtest run, so at best these repeated
calls are redundant. At worst, it triggered the regrtest abort because
the value of arg[0] was changed by one of the tests.
As it turns out, the testdir argument is never actually referenced in
the body of runtest_inner. runtest_inner in turn is called only by
runtest, which uses _its_ testdir argument only in the call to
runtest_inner.
Attached are two patches. The first just removes testdir from
runtest_inner, the second removes it from runtest as well. On my Gentoo
linux box the full (-uall) test suite passes with either patch applied.
(With the exception of test_ttk_guionly, which failed before the patch
at as well.) |
|
Date |
User |
Action |
Args |
2009-10-04 19:41:51 | r.david.murray | set | recipients:
+ r.david.murray |
2009-10-04 19:41:50 | r.david.murray | set | messageid: <1254685310.19.0.164822003436.issue7056@psf.upfronthosting.co.za> |
2009-10-04 19:41:48 | r.david.murray | link | issue7056 messages |
2009-10-04 19:41:47 | r.david.murray | create | |
|