Closed
Bug 612789
Opened 14 years ago
Closed 14 years ago
devicemanager can't function after dm.removeDir(devRoot)
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Unassigned)
References
Details
We're running dm.removeDir(devRoot) immediately before the installApp stuff so we know the device is clean. Despite attempting to dm.mkDir(devRoot), dm.mkDirs(devRoot), dm.mkDirs(os.path.join(devRoot, "tests")), nothing seems to work. I think it's automatically trying to chdir to devRoot before doing anything, and when that fails, it fails out.
Reporter | ||
Comment 1•14 years ago
|
||
My current workaround: adb shell mkdir /mnt/sdcard/tests + comment out the dm.removeDir(devRoot) step.
Reporter | ||
Comment 2•14 years ago
|
||
This may be fixed by bug 611348.
Comment 3•14 years ago
|
||
Was this fixed by bug 611348?
Comment 4•14 years ago
|
||
the errors found here are fixed in a series of other fixes (sutagent, devicemanager, install scripts). But 611348 is the most likely candidate for fixing this. :mw22, are you seeing these problems still?
Reporter | ||
Comment 5•14 years ago
|
||
Well, I'm not exactly sure what fixed it, but we are currently dm.removeDir(devRoot) during cleanup.py, and we just went green. So I'm marking this fixed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
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
•