python runtests doesn't work for me "Cannot initialize the application correctly"

VERIFIED FIXED

Status

Testing
Mochitest
VERIFIED FIXED
10 years ago
10 years ago

People

(Reporter: Martijn Wargers (zombie), Assigned: Waldo)

Tracking

Trunk
x86
Windows XP
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
I'm trying to use python runtests.py, but it doesn't seem to work for me.
I get a "Cannot initialize the application correctly, click OK to terminate the application" error (this was a rough translation of the (dutch) error dialog).

I'm on windowsXP, using mozilla-build.

$ python runtests.py
### XPCOM_MEM_LEAK_LOG defined -- logging leaks to C:\mozilla-build\mozilla\leak.log
Server pid: 772
Application pid: 1280
FAIL Exited with code -1072365564 during test run
 started: 2008-02-12 01:56:49.984000
finished: 2008-02-12 01:56:54.859000

perl runtests.pl works fine for me.
(Assignee)

Comment 1

10 years ago
Created attachment 302742 [details] [diff] [review]
Potential patch

I remember hitting this error or something like it during initial testing on Windows and fixing it; not sure what happened since.  This should fix the problem, and it's actually a bit better in terms of doing things the right way in allowing overriding anything (although it breaks the previous modularity a tad).
Assignee: nobody → jwalden+bmo
Status: NEW → ASSIGNED
Attachment #302742 - Flags: review?(sayrer)

Comment 2

10 years ago
Comment on attachment 302742 [details] [diff] [review]
Potential patch

ah Python, sweet Python

Perl is not missed
Attachment #302742 - Flags: review?(sayrer) → review+
(Assignee)

Comment 3

10 years ago
Fixed.  (Die, Perl, die!)
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
(Reporter)

Comment 4

10 years ago
Yes, it works now, thanks.
Status: RESOLVED → VERIFIED
Component: Testing → Mochitest
Product: Core → Testing
QA Contact: testing → mochitest
You need to log in before you can comment on or make changes to this bug.