On 2/21/06, Neal Norwitz <[EMAIL PROTECTED]> 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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
