Closed
Bug 637138
Opened 14 years ago
Closed 14 years ago
Fix Ubuntu 10.10 VM on QA-Horus to stop test breakage
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: whimboo, Unassigned)
References
Details
As we have seen in the last days a couple of tests across all supported branches of Firefox are failing on this machine. Doing release tests on QA-Set none of those failures show up. We should fix the Ubuntu 10.10 VM to stop those failures no-one can explain.
In the past I have already used a fresh 10.10 VM, and beginning of last week I have copied the one over from QA-Set, but without shutting down Fusion completely. Not sure if that could be related to this problem.
Al, could you please copy the 10.10 VM in a clean way from Set to Horus? If the failures will still be present, something on the host has to be broken, i.e. settings of Fusion or others.
Anthony, please add all the dependencies which are related to this VM. I probably have forgotten some.
Comment 1•14 years ago
|
||
There is a new VM in /data/vms/ on horus called "new ubuntu 10.10." Try that one. It is an updated, current 10.10 vm from set.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•14 years ago
|
||
The bug has to stay open until we can prove it has been really fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•14 years ago
|
||
Well, no. I resolve the bug *then* you go either reopen it if it isn't fixed or mark it verified if it isn't.
The bug can be in a resolved state pending verification.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 4•14 years ago
|
||
I meant "mark it verified if it is" above.
In any case, this is what we do with any other bug.
Reporter | ||
Comment 5•14 years ago
|
||
Ok, so we are much cleaner now in our results. Marking as verified fixed.
Status: RESOLVED → VERIFIED
Updated•6 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
•