Closed
Bug 418710
Opened 17 years ago
Closed 17 years ago
Tests aren't compiled during running runtests.py.
Categories
(Tamarin Graveyard :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: evgeniy.andrievskiy, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier:
During running testsuite (runtests.py) every test fails because of compiling error:
"compiling ...
FAILED! file not found ..."
Note: compilation isn't performed from the runtests.py despite of successful compiling in a standalone way. also there's no compiling info (output) in verbose mode during runtests.py executing.
Reproducible: Always
Steps to Reproduce:
1. set all required environment variables
2. change runtests.py line 283
cputype={'i386':'x86','i686':'x86','Power Macintosh':'ppc'}[platform.machine()]
to
cputype='x86'
(see bug 418640)
3. run runtests.py
Actual Results:
1 test output example:
1812 running .\as3\AbcDecoder\accessSpecifiers.as
compiling accessSpecifiers.as java -jar c:\Tamarin\tamarin-central\utils\asc.jar -import c:\Tamarin\tamarin-central\core\builtin.abc -in .\shell.as -in .\as3\AbcDecoder\accessSpecifiers\varsDef.as .\as3\AbcDecoder\accessSpecifiers.as FAILED! file not found .\as3\AbcDecoder\accessSpecifiers.abc
C:\Tamarin\tamarin-central\platform\win32\obj_8\shell\Debug_Debugger\avmplus_sd.exe .\as3\AbcDecoder\accessSpecifiers.abc FAILED passes:0 fails:1 unexpected passes: 0 expected failures: 0
I think, the source of the problem is run_pipe(cmd) method. It doesn't spawn process properly, so being returned output is empty.
The problem is solved by using subprocess.call(...).
PS problem occurs when using pythons 2.4.3 & 2.5.1
Comment 1•17 years ago
|
||
Must be run via cygwin.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•