Closed Bug 461337 Opened 11 years ago Closed 11 years ago
Sunbird tinderboxen need more disk space to stay green
Sunbird (but not Lightning) tinderboxen are aflame on Linux & Windows, see http://tinderbox.mozilla.org/showbuilds.cgi?tree=Sunbird&hours=24
Logs say: 'No space left on device'
Component: Sunbird Only → Build Config
QA Contact: sunbird → build
Yes, with the nightlies eating up upwards of 4-5 G this is hapenning with a build area of only 15G 4.2G buildbot/comm-central-calendar-linux/ 4.1G buildbot/comm-central-calendar-linux-nightly/ 3.7G buildbot/comm-central-sunbird-linux/ 1.2G buildbot/comm-central-sunbird-linux-l10n-full/ 4.0G buildbot/comm-central-sunbird-linux-nightly/ The nightlies wipe themselves once they are done, but while they are not done, that's close to 8Gb being eaten up. Since these 2 boxes are VMs, I'll file an IT request to get the disk size increased.
Filed disk size increase bugs
Mac tbox has gone aflame too. I don't understand the log, sorry (looks like Sanskrit to me). :-(
Updating Summary which didn't reflect reality anymore, and adding meta keyword. At least one Lightning box has gone aflame. Please add dependent bugs if necessary for other VMs and/or independent bugs for flames not related to disk space scarcity (if there are any).
Summary: Sunbird (but not Lightning) tinderboxen aflame on Linux & Windows → Several Sunbird tinderboxen aflame (no space left on device)
Not sure what OS X build you were referring to, but right now, all builders are green, except nightlies. Nightlies have failed because of lack of disk space in some cases, and would have failed anyways, because the configured username to upload update snippets to aus2-community was wrong.
Yeah, it was the nightly. Currently I see flames for the following: Linux comm-central sunbird nightly Linux comm-central-calendar ltn nightly MacOSX 10.4 comm-central sunbird nightly Win2k3 comm-central sunbird nightly Not sure which ones (other than the two you already filed) are dependent on this bug and/or merit a separate server-ops bug.
Summary: Several Sunbird tinderboxen aflame (no space left on device) → Sunbird nightly tinderboxen aflame (no space left on device)
Nope, the nightlies that ran out of disk space are accounted for in the blocking bugs, the others should go green tonight, as I've fixed the aus2 username bug.
All calendar-trunk ("Sunbird") boxen are now green _except_ that MacOsX box, which however hasn't run since 2008-10-23 09:20. AFAICT, the error log seems to indicate a password failure on uploading the snippet. What's the number of that aus2 username bug again?
The OSX lightning nightly is still running right now, with the sunbird one waiting for it to complete to run, and should turn green. For the aus2 username, there was no bug, but the changed revision is here: http://hg.mozilla.org/build/buildbot-configs/rev/268eb5251f86
Summary: Sunbird nightly tinderboxen aflame (no space left on device) → Sunbird tinderboxen need more disk space to stay green
(In reply to comment #10) [...] > For the aus2 username, there was no bug, but the changed revision is here: > > http://hg.mozilla.org/build/buildbot-configs/rev/268eb5251f86 Ah, so that's why I couldn't find it however hard I tried; and, yeah, you aren't the first one to get hit by case-sensitivity. :-)
OK, should this be fixed? Win32 builds are green. Linux bustage is tracked with Bug 462393. Macosx bustage complains about a different issue (Could not get lockfile /builds/buildbot/comm-central-sunbird-macosx/build/objdir-tb/ppc/mozilla/config/final-link-libs.lck. Remove file to clear up).
After this change, the Macosx is back to the same bustage as Linux (bug 462393)
Can we close this bug? Or at least rename the summary if still useful to track overall status of sunbird builds ?
(In reply to comment #15) > Can we close this bug? Or at least rename the summary if still useful to track > overall status of sunbird builds ? Resolving FIXED. We should file separate bugs for new issues.
Status: NEW → RESOLVED
Closed: 11 years ago
Hardware: PC → All
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.