Closed
Bug 1088693
Opened 11 years ago
Closed 8 years ago
64bit Window 7 machines fail to remove firefox binary
Categories
(Mozilla QA Graveyard :: Infrastructure, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: andrei, Unassigned)
Details
All 64b Windows 7 machines are affected.
There are several testsruns with the following failure:
> 03:07:11 Report document created at 'http://mozauto.iriscouch.com/mozmill-release/5560c4beef382ba39c2500563564bb46'
> 03:07:11 *** Removing profile: c:\jenkins\workspace\release-mozilla-release_functional\data\profile
> 03:07:11 *** Uninstalling build: c:\jenkins\workspace\release-mozilla-release_functional\data\binary\firefox-33
> 03:08:12 Traceback (most recent call last):
> 03:08:12 File "c:\jenkins\workspace\release-mozilla-release_functional\mozmill-env-windows\python\Scripts\testrun_functional-script.py", line 9, in <module>
> 03:08:12 load_entry_point('mozmill-automation==2.0.8.1', 'console_scripts', 'testrun_functional')()
> 03:08:12 File "c:\jenkins\workspace\release-mozilla-release_functional\mozmill-env-windows\python\lib\site-packages\mozmill_automation\testrun.py", line 781, in functional_cli
> 03:08:12 exec_testrun(FunctionalTestRun)
> 03:08:12 File "c:\jenkins\workspace\release-mozilla-release_functional\mozmill-env-windows\python\lib\site-packages\mozmill_automation\testrun.py", line 764, in exec_testrun
> 03:08:12 cls().run()
> 03:08:12 File "c:\jenkins\workspace\release-mozilla-release_functional\mozmill-env-windows\python\lib\site-packages\mozmill_automation\testrun.py", line 364, in run
> 03:08:12 mozinstall.uninstall(self._folder)
> 03:08:12 File "c:\jenkins\workspace\release-mozilla-release_functional\mozmill-env-windows\python\lib\site-packages\mozinstall\mozinstall.py", line 196, in uninstall
> 03:08:12 raise Exception('Failure removing uninstall folder.')
> 03:08:12 mozinstall.mozinstall.UninstallError: Failed to uninstall c:\jenkins\workspace\release-mozilla-release_functional\data\binary\firefox-33
> 03:08:12 Build step 'Invoke XShell command' marked build as failure
> 03:08:12 Archiving artifacts
> 03:08:12 Email was triggered for: Failure - Any
> 03:08:12 Sending email for trigger: Failure - Any
> 03:08:13 Sending email to: mozmill-ci@mozilla.org
> 03:08:22 Finished: FAILURE
I've cleaned 2 of them yesterday (after the first occurrence), but it doesn't seem to help.
This needs to be investigated, as it might lead to workspace removal issues.
Might be related to recent Java or OS updates?
| Reporter | ||
Updated•11 years ago
|
OS: Mac OS X → Windows 7
Hardware: x86 → x86_64
Comment 1•11 years ago
|
||
What do you mean with cleaned-up yesterday? What has been done exactly? Also was Firefox still running? That could be the problem here. Which versions are affected? Also which testruns?
Flags: needinfo?(andrei.eftimie)
| Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #1)
> What do you mean with cleaned-up yesterday? What has been done exactly?
I removed the jenkins folder for for safety.
> Also was Firefox still running? That could be the problem here.
Not that I saw. (Maybe it was as the end of the testrun, it closed eventually, but it was enough to block the removal of the folder)
> Which versions are affected? Also which testruns?
Haven't seen a pattern. I would say all but I haven't closely checked.
Flags: needinfo?(andrei.eftimie)
Comment 3•11 years ago
|
||
Are those the same machines where we see the build timeout for the installer?
| Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #3)
> Are those the same machines where we see the build timeout for the installer?
I had the same thought initially, but unfortunately no, they seem unrelated.
The build timeout happened on mm-win-81-32-2, while this issue seems to be confined to 64bit win 7 machines.
Comment 5•8 years ago
|
||
We have never seen this again in the last years.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•7 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
•