Closed Bug 714837 Opened 13 years ago Closed 13 years ago

Needs for an OS X box for testing pulse triggered daily Mozmill test-runs

Categories

(Mozilla QA Graveyard :: Infrastructure, defect)

All
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: whimboo, Assigned: abillings)

References

Details

To be able to fully test the Pulse triggered daily Mozmill test-runs, I need a machine with OS X as host. It must be capable of handling about 3 running VMs. Requirements: * Enough RAM for 3 concurrently running VMs * All available VMs from QA being available on the machine Thanks
Blocks: 709052
You can use 'release8-osx-107.qa.mtv1.mozilla.com' for this. It does not have VMware installed currently. I will install it and update the bug when I do so and the VMs are copied over.
Details sent to Henrik. All VMs are available and VMware is set up. I've updated the VMs to be current and taken snapshots on them.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Thanks Al, it works perfect. Just for reference it is release1-osx-107.qa.mtv1.mozilla.com now.
Status: RESOLVED → VERIFIED
This should be release8. release1 is a different mac mini.
Al, this box is behaving badly in the last couple of days. Right now I even cant login anymore with screen because I only get a black screen. Also after not using the box for a while (>15min), I cannot access the Jenkins web ui anymore. Once I login again, it's available immediately. http://release8-osx-107.qa.mtv1.mozilla.com:8080/ Can you please have a look at the box? It seems to be have started between Jan 5th and 6th.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
The problem here were the energy settings which let the box fall into sleep after 15 minutes of inactivity. This shouldn't really be set by default. I have removed that restriction now and it seems to work.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.