Closed
Bug 500519
Opened 16 years ago
Closed 16 years ago
Mozmill runtest.py doesn't set the thunderbird.exe environment correctly on Windows
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rain1, Unassigned)
Details
(Whiteboard: [fixed in mozrunner trunk])
Right now I need to close Thunderbird to run Mozmill tests. I'm not sure if it's possible, but it'd be great if we could run Mozmill with the -no-remote flag.
Comment 1•16 years ago
|
||
from the current runtest.py:
def init_env(self):
self.base_env = dict(os.environ)
# note, we do NOT want to set NO_EM_RESTART or jsbridge wouldn't work
# avoid dialogs on windows
self.base_env['XPCOM_DEBUG_BREAK'] = 'stack'
# do not reuse an existing instance
self.base_env['MOZ_NO_REMOTE'] = '1'
I presume this is not working on Windows or the environment is falling down or something?
Reporter | ||
Comment 2•16 years ago
|
||
Yeah, looks like that doesn't work, and neither does XPCOM_DEBUG_BREAK. Adjusting summary to reflect what is probably the bug.
OS: All → Windows 7
Hardware: All → x86
Summary: Make mozmill use -no-remote if possible → Mozmill runtest.py doesn't set the thunderbird.exe environment correctly on Windows
Reporter | ||
Comment 3•16 years ago
|
||
The bug's in mozrunner -- filed <http://code.google.com/p/mozrunner/issues/detail?id=7>.
Reporter | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [fixed in mozrunner trunk]
You need to log in
before you can comment on or make changes to this bug.
Description
•