Weird failure of test.py as testit.py
To avoid a conflict between tool/test.py and a potential directory tool/test, I have renamed test.py to testit.py and made a corresponding change to test_all.py . Before I checked the change in, all tests, invoked from testit.py or test_all.py, ran. After checking in the changed files I noticed that the tests no longer ran. That is, testit.py would start but find no tests. Eventually I found out that everything worked as long as test.py or test.pyc remained in the tool directory. (So copying testit.py to test.py makes you again able to run the tests.) So I had checked my changes, finding everything working, checked in, and cleaned away test.py* . Thus, I didn't notice that something had gone astray before committing the changes. Now there's the question what's wrong with test.py/testit.py . I suspected an import of "test" from within the module but found no such import. I'm still searching for the cause of the problem, but if someone has a quick idea, it would be fine if he/she responded on the list or even fixed the problem. Stefan
On Tue, 2003-12-23 22:17:12 +0100, Stefan Schwarzer wrote:
Now there's the question what's wrong with test.py/testit.py . I suspected an import of "test" from within the module but found no such import. I'm still searching for the cause of the problem, but if someone has a quick idea, it would be fine if he/she responded on the list or even fixed the problem.
One addition: I tracked down the problem to line 247 in test(it).py . If test.py* doesn't exist, the returned subsuite is empty. I'm trying to find out, why. (If it wasn't clear from my previous mail: you can reproduce everything without involving test_all.py .) Stefan
[Stefan Schwarzer Tue, Dec 23, 2003 at 10:33:38PM +0100]
On Tue, 2003-12-23 22:17:12 +0100, Stefan Schwarzer wrote:
Now there's the question what's wrong with test.py/testit.py . I suspected an import of "test" from within the module but found no such import. I'm still searching for the cause of the problem, but if someone has a quick idea, it would be fine if he/she responded on the list or even fixed the problem.
One addition: I tracked down the problem to line 247 in test(it).py . If test.py* doesn't exist, the returned subsuite is empty. I'm trying to find out, why.
Well, you forgot to change about 50 other files <wink>. See my fixes http://codespeak.net/pipermail/pypy-svn/2003-December/001851.html which shows that all test files (and even some others needing to parse options) use the test (now testit) module. Please be careful when changing the foundation of our development model :-) cheers, holger
On Wed, 2003-12-24 00:08:12 +0100, holger krekel wrote:
[Stefan Schwarzer Tue, Dec 23, 2003 at 10:33:38PM +0100]
On Tue, 2003-12-23 22:17:12 +0100, Stefan Schwarzer wrote:
Now there's the question what's wrong with test.py/testit.py . I suspected an import of "test" from within the module but found no such import. I'm still searching for the cause of the problem, but if someone has a quick idea, it would be fine if he/she responded on the list or even fixed the problem.
One addition: I tracked down the problem to line 247 in test(it).py . If test.py* doesn't exist, the returned subsuite is empty. I'm trying to find out, why.
Well, you forgot to change about 50 other files <wink>. See my fixes
http://codespeak.net/pipermail/pypy-svn/2003-December/001851.html
which shows that all test files (and even some others needing to parse options) use the test (now testit) module. Please be careful when changing the foundation of our development model :-)
*blush* I can't understand why I didn't note that simple reason. On the other hand, testit.py didn't output any error messages, so I expected something subtle going on and didn't get to that trivial cause first. Many thanks for the quick fix! Stefan
[Stefan Schwarzer Wed, Dec 24, 2003 at 11:43:06AM +0100]
On Wed, 2003-12-24 00:08:12 +0100, holger krekel wrote:
[Stefan Schwarzer Tue, Dec 23, 2003 at 10:33:38PM +0100]
On Tue, 2003-12-23 22:17:12 +0100, Stefan Schwarzer wrote:
Now there's the question what's wrong with test.py/testit.py . I suspected an import of "test" from within the module but found no such import. I'm still searching for the cause of the problem, but if someone has a quick idea, it would be fine if he/she responded on the list or even fixed the problem.
One addition: I tracked down the problem to line 247 in test(it).py . If test.py* doesn't exist, the returned subsuite is empty. I'm trying to find out, why.
Well, you forgot to change about 50 other files <wink>. See my fixes
http://codespeak.net/pipermail/pypy-svn/2003-December/001851.html
which shows that all test files (and even some others needing to parse options) use the test (now testit) module. Please be careful when changing the foundation of our development model :-)
*blush*
I can't understand why I didn't note that simple reason. On the other hand, testit.py didn't output any error messages, so I expected something subtle going on and didn't get to that trivial cause first.
Yeah, such behaviour is really bad and one of the reasons we are rewriting the whole mess :-) cheers, holger
participants (2)
-
holger krekel
-
Stefan Schwarzer