[Python-Dev] freeze build slave

[Antoine Pitrou]

On Sun, 30 Mar 2014 20:44:02 +0200
"Martin v. Löwis" <martin at v.loewis.de> wrote:
> I have created a buildbot configuration to test freeze. At the moment,
> it has only one builder:
> 
> http://buildbot.python.org/all/waterfall?show=AMD64%20Ubuntu%20LTS%20Freeze%203.x
> 
> which currently fails as freeze doesn't actually work.
> 
> The test itself works by first building Python in release mode,
> then installing it, then running freeze on a test program, then
> building the test programm (and ultimately running it).
> 
> The question then is: how should that integrate with the rest
> of the builders? I can see three alternatives:
> A. (status quo) run the test on a selected subset of the Unix
>    builders
> B. run the test on all Unix builders.
> C. integrate the test with the Unix regular Unix builder
> 
> Evaluating these alternatives:
> B: pro: wider testing
>    con: each such build takes the slave lock, so slaves
>    will have to do one additional full build per commit
>    (or two if the fix gets checked into 3.4 as well).
>    In addition, each slave will need disk space for one
>    additional build tree plus one Python installation,
>    per branch.
> C: pro: compared to B, build time is reduced (need only
>    to build once per branch); disk space is also reduced
>    con: it would test a debug build, not a release build

We have at least one builder working in release (i.e. non-debug) mode.
http://buildbot.python.org/all/builders/x86%20Gentoo%20Non-Debug%203.x

Regards

Antoine.