Closed
Bug 463707
Opened 17 years ago
Closed 17 years ago
Talos doesn't fully clean up profile directories?
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Dolske, Unassigned)
Details
Rob wondered during a discussion if Talos was cleaning up both profile directories. On Windows and OS X, profiles are split into two locations:
OS X:
~/Library/Application\ Support/Firefox/Profiles/
~/Library/Caches/Firefox/Profiles/
Windows XP:
C:\Documents and Settings\(user)\Application Data\Mozilla\Firefox\Profiles
C:\Documents and Settings\(user)\Local Settings\Application Data\Mozilla\Firefox\Profiles
Looking at the Talos code, it only seems to create and remove one of these directories.
| Reporter | ||
Comment 1•17 years ago
|
||
Bah, filed in wrong component.
Component: Testing → Release Engineering: Talos
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
Comment 2•17 years ago
|
||
The talos code works from a standard clean profile - the browser doesn't create the profile per run but copies the standard profile to a new location and then provides the location to the browser through a command line switch. Would those secondary directories still get created with that work flow?
| Reporter | ||
Comment 3•17 years ago
|
||
Is Talos using "-P foo" or "-profile /bar/foo"? I think the split directories are only used with named (-P) profiles... Checking for the creation of a "Cache" directory in the testing profile would verify that. Or checking in the paths above.
Comment 4•17 years ago
|
||
Talos uses the "-profile /foo/bar" option. A quick check on a mac talos boxes selected at random does not indicate the presence of the directories mentioned above.
| Reporter | ||
Comment 5•17 years ago
|
||
Ok, good to know!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•