Closed Bug 870638 Opened 10 years ago Closed 6 years ago

ensure on windows that we remove appdata where crash reports end up

Categories

(Release Engineering :: General, defect)

All
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Unassigned)

Details

I was looking at some xperf data and noticed that we do some reading of crash reports, even though we don't have any crash reports on that current run.

We need to ensure that we clean up all files in:
C:\Users\cltbld\AppData\Roaming\Mozilla\firefox\Crash Reports\InstallTime2013*

In fact, we should probably wipe the entire directory:
C:\Users\cltbld\AppData\Roaming\Mozilla\

Is it possible that we have system level profiles stored on other platforms as well?
We're supposed to be doing some cleaning before buildbot starts [1]
del /F /Q C:\Users\cltbld\AppData\Roaming\Mozilla\Firefox\console.log
rmdir /S /Q C:\Users\cltbld\AppData\Local\Temp

[1] http://hg.mozilla.org/build/puppet-manifests/file/default/modules/buildslave/files/startTalos-w7.bat
oh cool, I see this:

REM Cleanup profile, temp, and log files.
del /F /Q C:\Users\cltbld\AppData\Roaming\Mozilla\Firefox\console.log
rmdir /S /Q C:\Users\cltbld\AppData\Local\Temp
mkdir C:\Users\cltbld\AppData\Local\Temp
rm c:\talos-slave\twistd.log.*


could we add:
rmdir /s /q c:\Users\cltbld\AppData\Roaming\Mozilla
I just tested that I can do it over SSH.
on my loaner ubuntu slave, I see:
ls -la ~/.mozilla/firefox/Crash\ Reports/pending/
total 1196
drwxr-xr-x 2 cltbld cltbld   4096 May 10 08:09 .
drwx------ 4 cltbld cltbld   4096 May  8 11:42 ..
-rw------- 1 cltbld cltbld 109168 May  8 12:40 07cb4c00-4b78-947f-5d146e56-59bf2d9f.dmp
-rw------- 1 cltbld cltbld    798 May  8 12:40 07cb4c00-4b78-947f-5d146e56-59bf2d9f.extra
-rw------- 1 cltbld cltbld  91184 May  3 12:24 231764c0-d98c-f589-7b0133f9-2b9b2be8.dmp
-rw------- 1 cltbld cltbld    798 May  3 12:24 231764c0-d98c-f589-7b0133f9-2b9b2be8.extra
-rw------- 1 cltbld cltbld  91520 May  8 12:00 2cda2c33-5da1-3e37-6dc053e2-4c3f0dfc.dmp
-rw------- 1 cltbld cltbld    798 May  8 12:00 2cda2c33-5da1-3e37-6dc053e2-4c3f0dfc.extra
-rw------- 1 cltbld cltbld  95256 May  3 13:51 3130e773-15f0-d602-7ee1c99a-5ce5fe99.dmp
-rw------- 1 cltbld cltbld    798 May  3 13:51 3130e773-15f0-d602-7ee1c99a-5ce5fe99.extra
-rw------- 1 cltbld cltbld  87064 May  3 14:36 47f73a31-6af9-1a51-617c7310-7db8f7fc.dmp
-rw------- 1 cltbld cltbld    798 May  3 14:36 47f73a31-6af9-1a51-617c7310-7db8f7fc.extra
-rw------- 1 cltbld cltbld  95256 May  3 15:22 50dcd164-b522-5b70-4e3e355f-7dd93dee.dmp
-rw------- 1 cltbld cltbld    798 May  3 15:22 50dcd164-b522-5b70-4e3e355f-7dd93dee.extra
-rw------- 1 cltbld cltbld  95672 May  8 12:40 56ddfdcc-2206-20d2-5247d282-7151ed54.dmp
-rw------- 1 cltbld cltbld    798 May  8 12:40 56ddfdcc-2206-20d2-5247d282-7151ed54.extra
-rw------- 1 cltbld cltbld  91160 May  3 16:08 58ba30fe-28eb-cb2e-49415f4d-6913c22e.dmp
-rw------- 1 cltbld cltbld    798 May  3 16:08 58ba30fe-28eb-cb2e-49415f4d-6913c22e.extra
-rw------- 1 cltbld cltbld  95672 May  8 12:19 592126d5-67ff-2b2b-33318baa-667ea698.dmp
-rw------- 1 cltbld cltbld    798 May  8 12:19 592126d5-67ff-2b2b-33318baa-667ea698.extra
-rw------- 1 cltbld cltbld  95256 May  3 16:54 73f50466-d56e-55ae-69a40815-37715cde.dmp
-rw------- 1 cltbld cltbld    798 May  3 16:54 73f50466-d56e-55ae-69a40815-37715cde.extra
-rw------- 1 cltbld cltbld  91184 May  3 12:55 7adafa3e-8543-016f-3e6d2d15-0887b8dc.dmp
-rw------- 1 cltbld cltbld    798 May  3 12:55 7adafa3e-8543-016f-3e6d2d15-0887b8dc.extra
-rw------- 1 cltbld cltbld  95672 May  8 12:40 7f3bc8bd-42e0-c6d4-7e556e63-76485f50.dmp
-rw------- 1 cltbld cltbld    798 May  8 12:40 7f3bc8bd-42e0-c6d4-7e556e63-76485f50.extra
cltbld@tst-jmaher-ubuntu32-001:~/jmaher$ 

We really should be cleaning this up as well.  I assume we have data laying around on all operating systems!
Assignee: nobody → armenzg
I'm looking at my queue and I don't have time for this for a while.
Assignee: armenzg → nobody
Whiteboard: [buildduty]
Whiteboard: [buildduty]
Product: mozilla.org → Release Engineering
Any ideas if this is still an issue?
Flags: needinfo?(jmaher)
I don't think this is an issue anymore.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jmaher)
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.