Building all ports when setting up a new buildbot builder

[Joshua Root]

On 2014-12-4 01:51 , Daniel J. Luke wrote:
>> On Dec 2, 2014, at 9:38 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>> On Dec 2, 2014, at 8:40 AM, Daniel J. Luke wrote:
>>> this seems like a reasonable workaround, but it might be nice if we could make building 'all' ports work
>>
>> It seemed to be an out of memory error relating to stderr and stdout. I'm not surprised that the entire combined debug output of building all 20,000 ports might be a bit too much data to process all at once.
> 
> ick, so maybe something is capturing all stderr/stdout to memory while each step is being run (instead of logging it to a file or filling a small buffer and then writing it out when it gets full)?

Would have to check the buildbot source. Seems like they would have
thought of large logs and handled them appropriately, but maybe not.

> Also, even so, is it a 64bit process? I would be surprised if it's actually running out of virtual memory space (but maybe the virtual machine it's running on is configured with some strict resource limits?).

Yes, it should be 64-bit. Giving the buildmaster more swap or raising
resource limits may well help.

- Josh