Closed Bug 687877 Opened 14 years ago Closed 14 years ago

change clientproxy startup from manual to launchd based script

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bear, Assigned: bear)

References

(
URL
)

Details

(Whiteboard: [android][tegra])

currently clientproxy is started manually and for a lot of small reasons this is not optimal
URL: http://trac.buildbot.net/wiki/UsingLa...
Whiteboard: [android][tegra]
Bear, are you going to be looking at this soon?
yes. oh! thought I had assigned this to me already... sorry!
Assignee: nobody → bear
with the move to a foopy-less environment, the tegras will not have osx slaves (plus buildbot slave is already started using launchd) while this still exists as a problem that sometimes happens, I'm wanting to close this so that we can work on foopy-less code instead of this workaround
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.