Wednesday, 30. August 2006 00:27.
Test 73 fails and I have no idea why:
T:\svnwork\lino\trunk\tests>lino runtests 73
Lino/runtests
Copyright (c) 2004-2006 Luc Saffre.
This software comes with ABSOLUTELY NO WARRANTY and is
distributed under the terms of the GNU General Public License.
See file COPYING.txt for more information.
Using Lino 0.6.19, Python 2.3.4 final
found 1 cases and 0 suites.
.F
======================================================================
FAIL: test02 (73.Case)
———————————————————————-
Traceback (most recent call last):
File "T:\svnwork\lino\trunk\tests\73.py", line 70, in test02
self.trycmd(cmd)
File "T:\svnwork\lino\trunk\tests\73.py", line 50, in trycmd
"%r failed: close() returned %r, stdout is %r." File "c:\Python23\lib\unittest.py", line 302, in failUnlessEqual
raise self.failureException, AssertionError: 'lino prn2pdf -b -o "c:\\docume~1\\luc\\locals~1\\temp
\\4.pdf" "c:\\drives\\t\\svnwork\\lino\\trunk\\tests\\testdata\\textpr
inter\\4.prn"' failed: close() returned 1, stdout is ''.
———————————————————————-
Ran 2 tests in 4.948s
I don't understand why the fourth command fails when launched via os.popen(). If I launch the same command manually or from a batch file, it always works. For example:
@echo off call lino prn2pdf -b -o "c:\docume~1\luc\locals~1\temp\4.pdf" "c:\drives\t\svnwork\lino\trunk\tests\testdata\textprinter\4.prn" echo %errorlevel%
This will output 0.
It must have to do with the content of file 4.prn because if I do...
ren 4.prn tmp.prn ren 2.prn 4.prn ren tmp.prn 2.prn
...and run the test again, then it fails on 2.prn.
Refering articles:
- "workaround" for tests 73 (30.08.06) — I cheated to work around Test 73 fails (30.08.06) by removing file 4.prn from the list of files to be tested. I still have no explanation for this phenomen. To be continued.