Closed
Bug 609193
Opened 14 years ago
Closed 14 years ago
maemkit fails to run browser chrome tests on fennec
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: jmaher)
Details
(Whiteboard: [mobile_unittests])
Attachments
(1 file, 1 obsolete file)
3.03 KB,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
it appears that maemkit is failing to run browser chrome tests on fennec. It generates the correct command line, but when launching python from subprocess.Popen(...) it launches fennec and a couple tests later fennec hangs until it times out after an hour. With the refactoring (early this year) of the mochitest harnesses, we can now easily run the browser-chrome harness just like the original script without much hacking. This patch is isolated, but is a hack in the sense that we just import the classes for mochitest and then copy over the config data to the options variable before running the tests.
Attachment #487807 -
Flags: review?(aki)
Comment 1•14 years ago
|
||
Comment on attachment 487807 [details] [diff] [review] launch commands directly instead of with subprocess.Popen (1.0) Could we get an error message before that sys.exit(1) ? *STAMP* with that.
Attachment #487807 -
Flags: review?(aki) → review+
Assignee | ||
Comment 2•14 years ago
|
||
those messages will come from the parser.verifyOptions() call. I have added a maemkit specific message there.
Assignee: nobody → jmaher
Attachment #487807 -
Attachment is obsolete: true
Attachment #487873 -
Flags: review+
Assignee | ||
Comment 3•14 years ago
|
||
http://hg.mozilla.org/qa/maemkit/pushloghtml?changeset=9c773fe1d3f2
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: New Frameworks → General
You need to log in
before you can comment on or make changes to this bug.
Description
•