Re: Further adventures in the land of 64-bit linux

> [Anders Qvist]
> > Maybe the farm should compile with pydebugging?
> 
> Testing a release build is crucial, because that's what end users use, and
> it's the only way to provoke platform compiler optimization bugs.
> 
> Of all the build variations beyond that, --with-pydebug is by far the most
> valuable to try.  In the 2.3 line, it's especially valuable to do a debug
> build because it triggers new memory management code in Python that can
> catch many kinds of insanity (reading/writing out of bounds, reading
> uninitialized heap memory, reading heap memory that's already been free()ed,
> ...) early.
> 
> Which build variations beyond that to try may depend on how much resource
> the PBF is willing to throw at them.

Ah, they are Lysator's resoures, which means that Lysator and not the
PBF gets to decide how the machines get used.  We now have a procedure
for adding machines to run test builds outside of Lysator, so perhaps
we will get more machines that way. But the bottleneck is the time of
Lysator volunteers, and the cpu cycles of machines that Lysator uses
for other purposes.

Laura