build.macports.org unavailable again

[Joshua Root]

On 2013-12-10 18:34 , William Siegrist wrote:
> 
> On Dec 8, 2013, at 9:11 PM, Joshua Root <jmr at macports.org> wrote:
> 
>> It got further on the second run so I doubt it's a specific port. Ports
>> that were already built are skipped, and ports that failed previously
>> are skipped during 'all' runs unless the portfile has been modified since.
>>
>> The buildmaster went down, not just the slave. (Again, there is no
>> "Mavericks buildbot", there is a Mavericks buildslave.) It hadn't got to
>> uploading any files yet so the only effect the slave could have on the
>> master is via log files and status reporting. The log is big, but it
>> seems unlikely it would be dumb enough to try to load the whole thing
>> into memory at once. We never had problems previously with logs from
>> full runs that would have been bigger than the partial runs here.
> 
> 
> Actually, IIRC, buildbot does do some memory-only storage like that. We can try throwing more memory at the master to accommodate. Perhaps Mavericks for whatever reason generates more log lines? Or adding Mavericks logs to the existing set of logs always being processed has put us past a tipping point? 

Could be. It'll be difficult to reproduce the problem on the production
system at this point. I guess someone could try making a slave generate
really big logs in a test setup and see what happens.

- Josh