In order to run robotium, we need to run 'am instrument <params>'. When running this via sutagent exec, we block on the call. Normally for exec, we don't block on org.mozilla.fennec or similar commands. We can work around this in the devicemanager and python harness code, but it would be nice to fix this in sutagent. For example, here is code that makes it work by hacking the harnesses: --- a/build/mobile/remoteautomation.py Thu Jan 12 15:34:16 2012 -0500 +++ b/build/mobile/remoteautomation.py Thu Jan 12 15:34:36 2012 -0500 @@ -156,7 +156,10 @@ self.stdoutlen = 0 self.proc = dm.launchProcess(cmd, stdout, cwd, env, True) if (self.proc is None): - raise Exception("unable to launch process") + if cmd == 'am': + self.proc = stdout + else: + raise Exception("unable to launch process") exepath = cmd name = exepath.split('/')[-1] self.procName = name
Patch to do my little hack mentioned in my comments. In discussing on IRC with :gbrown, there are similar issues while running xpcshell tests via SUT agent and it would be nice to solve this in a bigger picture. For the sake of getting things going, this patch will allow us to run end to end on SUT agent once it is landed. A better solution in the near term is to resolve the launching (probably a change to SUTAgent) and work on rolling out an update to the tegras when we get a chance.
Attachment #588279 - Flags: review?(gbrown)
Try run for 8b767bc75058 is complete. Detailed breakdown of the results available here: https://tbpl.mozilla.org/?tree=Try&rev=8b767bc75058 Results (out of 29 total builds): success: 23 warnings: 6 Builds (or logs if builds failed) available at: http://firstname.lastname@example.org
4 warnings are ignored tests, and the other 2 are random oranges.
Comment on attachment 588279 [details] [diff] [review] allow 'am' commands to execute and wait (1.0) Review of attachment 588279 [details] [diff] [review]: ----------------------------------------------------------------- Seems harmless!
Attachment #588279 - Flags: review?(gbrown) → review+
Thanks Geoff, we will land this today and work on defining a better solution.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Assignee: nobody → jmaher
Target Milestone: --- → mozilla12
You need to log in before you can comment on or make changes to this bug.