Closed Bug 730153 Opened 9 years ago Closed 9 years ago

SUT agent KILL command fails to kill xpcshell

Categories

(Testing :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla13

People

(Reporter: gbrown, Assigned: gbrown)

References

Details

Attachments

(1 file)

In bug 705192, I try to use the devicemanager kill command to clean up any xpcshell processes that may have hung. With SUT, that fails: hung xpcshell processes continue to live.

I think the issue is that the SUT agent uses getRunningAppProcesses to examine which processes are currently running and it appears to only return android application names, like org.mozilla.fennec.
Blocks: 705192
See also bug 729552
Assignee: nobody → gbrown
In this patch, if the KILL command does not find a matching application, it now continues to search for a matching process by checking the "ps" command output.

I found that I could not kill xpcshell with "su -c kill <pid>" or even "su -c kill -9 <pid>"...both failed silently. However, a simple "kill <pid>" worked just fine. I don't understand why the su commands fail. (Also, the su commands successfully kill xpcshell if executed from adb shell.) It makes sense to me that su should not be needed: xpcshell is a child process of the sutagent, so sutagent should be able to kill it without special privileges.
Attachment #601301 - Flags: review?(jmaher)
Comment on attachment 601301 [details] [diff] [review]
patch to kill non-Java processes

Review of attachment 601301 [details] [diff] [review]:
-----------------------------------------------------------------

note that we will have to build an agent and deploy it in staging, then roll it out to all the tegras before tests which depend on this can land.
Attachment #601301 - Flags: review?(jmaher) → review+
https://hg.mozilla.org/mozilla-central/rev/5bbffabdc291
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla13
You need to log in before you can comment on or make changes to this bug.