Closed Bug 598914 Opened 14 years ago Closed 14 years ago

Upgrade memory for SeaMonkey build slaves

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kairo, Assigned: phong)

References

Details

When we switched to libxul and turned on IPC yesterday, our Linux build slaves, which currently have 2GB of RAM and 512MB of swap, decided to start failing with "Memory exhausted" when linking debug libxul.

This seems to mean that we need to upgrade their available memory and do that quite fast. Sorry for coming around with that urgency, but I was not aware myself that 2GB of RAM could be too less until an hour ago or so.

We should try to upgrade them to be on par with what Firefox build slaves have right now, but I don't know what that is exactly, couldn't reach anyone with that knowledge at this hour.

The affected Linux slaves are all VMs, cb-seamonkey-linux-01 through -03 and cb-seamonkey-linux64-01 on the Parallels host, cb-sea-linux-tbox on a San Jose community ESX host and cn-sea-qm-centos5-01 on the Amsterdam L10n ESX host.


Only Linux is failing right now, but we probably need to look into upgrading the other OSes as well after the urgency has gone away.
This should be "SeaMonkey" not "Mozilla.org" will some1 correct this?
(In reply to comment #2)
> This should be "SeaMonkey" not "Mozilla.org" will some1 correct this?

No our servers are hosted at Mozilla, and their IT would need to do this. The bug is filed correctly.
As this is currently causing us to have no tests run on Linux, bumping severity of this bug.
Severity: normal → critical
From IRC it sounds like phong is working on this.  Assigning it so it'll stop paging me.
Assignee: server-ops → phong
bumped all of these up to 3 GB.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
V.Fixed, as we now have green builds.
Status: RESOLVED → VERIFIED
Reopening as cb-seamonkey-linux-02 seems to be back at 2 GB (or hasn't been upgraded correctly). We have shut down -03 for the moment, so the host should be able to handle this.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Blocks: 599302
Linux-02 is now back to 3 GB.  I had to lower Linux64-01 down to 2GB to accommodate Linux-02.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.