Closed
Bug 860677
Opened 12 years ago
Closed 12 years ago
Remove already downloaded but not removed updates at the end of update tests
Categories
(Mozilla QA Graveyard :: Mozmill Automation, defect)
Mozilla QA Graveyard
Mozmill Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
Attachments
(1 file)
|
1.31 KB,
patch
|
davehunt
:
review+
|
Details | Diff | Splinter Review |
While investigating bug 803489 I have seen that in cases of aborts already downloaded updates still exist and can cause problems the next time we trigger an update test. We have to remove those files at the end of the testrun.
| Assignee | ||
Comment 1•12 years ago
|
||
So we have to retrieve the update path from Firefox and delete everything in the automation script. That re-instantiates bug 842571 in some way.
After digging around I have found that with bug 750554 we got the getUpdatesDirectory() on the AUS service, which certainly helps us here and also could be used to fix bug 842571.
| Assignee | ||
Comment 2•12 years ago
|
||
Patch for review. It works fine on Linux, but I will still have to test on OS X and Windows. Dave mind reviewing it already? Also I would appreciate if you could test on OS X given that I don't have an OS X box today. Thanks.
Attachment #736305 -
Flags: review?(dave.hunt)
| Assignee | ||
Comment 3•12 years ago
|
||
I did further tests on Windows and Mac and on both platforms it works fantastic. We successfully remove the update folder after our tests. On the affected Win8 machine I can't even replicate the jsbridge failure anymore. So it looks like this patch will indeed add a lot more stability to our tests.
Comment 4•12 years ago
|
||
Comment on attachment 736305 [details] [diff] [review]
Patch v1
Review of attachment 736305 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good!
Attachment #736305 -
Flags: review?(dave.hunt) → review+
| Assignee | ||
Comment 5•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•