maemkit fails to run browser chrome tests on fennec

RESOLVED FIXED

Status

Testing
General
RESOLVED FIXED
7 years ago
29 days ago

People

(Reporter: jmaher, Assigned: jmaher)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [mobile_unittests])

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

7 years ago
Created attachment 487807 [details] [diff] [review]
launch commands directly instead of with subprocess.Popen (1.0)

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

7 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

7 years ago
Created attachment 487873 [details] [diff] [review]
launch commands directly instead of with subprocess.Popen (1.1)

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

7 years ago
http://hg.mozilla.org/qa/maemkit/pushloghtml?changeset=9c773fe1d3f2
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Component: New Frameworks → General
Product: Testing → Testing
You need to log in before you can comment on or make changes to this bug.