RetroSearch Browse

Wed Feb 22 09:10:43 CET 2006 · https://mail.python.org/pipermail/python-dev/2006-February/061689.html

On 2/21/06, Neal Norwitz <nnorwitz at gmail.com> wrote:
>
> I agree with this, but don't know a clean way to do 2 builds.  I
> modified buildbot to:
>
>  - Stop doing the second "without deleting .py[co]" run.
>  - Do one run with a debug build.
>  - Use -uall -r for both.

I screwed it up, so now it does:

  - Do one run with a debug build.
  - Use -uall -r for both.
  - Still does the second "deleting .py[co]" run

I couldn't think of a simple way to figure out that on most unixes the
program is called python, but on Mac OS X, it's called python.exe.  So
I reverted back to using make testall.  We can make a new test target
to only run once.

I also think I know how to do the "double builds" (one release and one
debug).  But it's too late for me to change it tonight without
screwing it up.

The good/bad news after this change is:

http://www.python.org/dev/buildbot/all/g4%20osx.4%20trunk/builds/145/step-test/0

A seg fault on Mac OS when running with -r. :-(

n

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-February/061689.html below:

[Python-Dev] buildbot vs. Windows