Re: [Python-Dev] Windows buildbot (Was: buildbot failure in x86 W2k trunk)

[Thomas Heller]

Martin v. Löwis schrieb:
>> Should I try to setup another buildbot client for win32/AMD64?
> 
> We don't have a Win64 buildbot yet. Depending on whether you plan
> to use PCbuild or PCbuild8, this might be a challenge to get working
> (I think it's a challenge either way, but different).
> If it could actually work, it might be useful.

For release25-maint, probably PCBuild should be used since that is used to 
create the installer.
For trunk/Python 2.6 I don't know what you will use for the release version.


Where do you think is the challange to get it working?  For the buildbot client 
itself
I would use the same stuff as in the WinXP buildbot (32-bit python2.4, twisted, 
buildbot,
pywin32).

For the build scripts in Tools\buildbot I made some small changes to the batch 
files (appended).
They look for a PROCESSOR_ARCHITECTURE env var, and if this is equal to AMD64 
the build target
and one or two small other things are changed from the default.  So these 
scripts currently build
the PCBuild process.

I can run Tools\buildbot\build.bat, then Tools\buildbot\test.bat, and 
Tools\buildbot\clean.bat
successfully.  Of course this does not mean that *everything* is built 
correctly - currently
_sqlite3, bz2, _tkinter, and _ssl are not build because of several reasons.

If you want me to go online with the buildbot please send me a HOST:PORT and 
PASSWORD.

Thomas

Index: Tools/buildbot/build.bat
===
--- Tools/buildbot/build.bat(revision 55792)
+++ Tools/buildbot/build.bat(working copy)
@@ -2,4 +2,6 @@
 cmd /c Tools\buildbot\external.bat
 call "%VS71COMNTOOLS%vsvars32.bat"
 cmd /q/c Tools\buildbot\kill_python.bat
-devenv.com /useenv /build Debug PCbuild\pcbuild.sln
+set TARGET=Debug
+if "%PROCESSOR_ARCHITECTURE%" == "AMD64" set _TARGET=ReleaseAMD64
+devenv.com /useenv /build %_TARGET% PCbuild\pcbuild.sln
Index: Tools/buildbot/test.bat
===
--- Tools/buildbot/test.bat (revision 55792)
+++ Tools/buildbot/test.bat (working copy)
@@ -1,3 +1,5 @@
 @rem Used by the buildbot "test" step.
 cd PCbuild
-call rt.bat -d -q -uall -rw
+set _DEBUG=-d
+if "%PROCESSOR_ARCHITECTURE%"=="AMD64" set _DEBUG=
+call rt.bat %_DEBUG% -q -uall -rw
Index: Tools/buildbot/clean.bat
===
--- Tools/buildbot/clean.bat(revision 55792)
+++ Tools/buildbot/clean.bat(working copy)
@@ -2,5 +2,9 @@
 call "%VS71COMNTOOLS%vsvars32.bat"
 cd PCbuild
 @echo Deleting .pyc/.pyo files ...
-python_d.exe rmpyc.py
-devenv.com /clean Debug pcbuild.sln
+set _PYTHON=python_d.exe
+if "%PROCESSOR_ARCHITECTURE%"=="AMD64" set _PYTHON=python.exe
+%_PYTHON% rmpyc.py
+set TARGET=Debug
+if "%PROCESSOR_ARCHITECTURE%" == "AMD64" set TARGET=ReleaseAMD64
+devenv.com /clean %TARGET% pcbuild.sln

___
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

Re: [Python-Dev] Windows buildbot (Was: buildbot failure in x86 W2k trunk)

[Martin v. Löwis]

> For release25-maint, probably PCBuild should be used since that is used to 
> create the installer.
> For trunk/Python 2.6 I don't know what you will use for the release version.

I actually don't know either, yet. I would like to use Orcas, but it's
not clear when this will be released; neither is clear when 2.6 will
be released.

I notice that Kristjan would like to see a PCbuild8 buildbot.

> Where do you think is the challange to get it working?  For the buildbot 
> client itself
> I would use the same stuff as in the WinXP buildbot (32-bit python2.4, 
> twisted, buildbot,
> pywin32).

I think the scripts in Tools\buildbot might be tricky, along with
possible changes to the master.

> For the build scripts in Tools\buildbot I made some small changes to the 
> batch files (appended).
> They look for a PROCESSOR_ARCHITECTURE env var, and if this is equal to AMD64 
> the build target
> and one or two small other things are changed from the default.  So these 
> scripts currently build
> the PCBuild process.

That's an interesting option. I had myself arranged for the master to
issue a different build command to an AMD64 build slave.

> If you want me to go online with the buildbot please send me a HOST:PORT and 
> PASSWORD.

Doing so in a separate message.

Regards,
Martin
___
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

[Python-Dev] Compiling 2.5.1 under Studio 11

[Ellinghaus, Lance]

Hello,

I am having a couple of issues compiling Python 2.5.1 under Sun Solaris
Studio 11 on Solaris 8.

Everything compiles correctly except the _ctypes module because it
cannot use the libffi that comes with Python and it does not exist on
the system.
Has anyone gotten it to compile correctly using Studio 11? I know it
will compile under GCC but I am not allowed to use GCC.

Also, during the pyexpat tests, Python generates a segfault. 

Are there any patches to fix these?

Thank you,

Lance


___
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

[Python-Dev] cProfile with generator throwing

[Eyal Lotem]

Hi. It seems that cProfile does not support throwing exceptions into
generators properly, when an external timer routine is used.

The problem is that _lsprof.c: ptrace_enter_call assumes that there
are no exceptions set when it is called, which is not true when the
generator frame is being gen_send_ex'd to send an exception into it
(Maybe you could say that only CallExternalTimer assumes this, but I
am not sure).  This assumption causes its eventual call to
CallExternalTimer to discover that an error is set and assume that it
was caused by its own work (which it wasn't).

I am not sure what the right way to fix this is, so I cannot send a patch.
Here is a minimalist example to reproduce the bug:

>>> import cProfile
>>> import time
>>> p=cProfile.Profile(time.clock)
>>> def f():
...   yield 1
...
>>> p.run("f().throw(Exception())")
Exception exceptions.Exception: Exception() in  ignored
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.5/cProfile.py", line 135, in run
return self.runctx(cmd, dict, dict)
  File "/usr/lib/python2.5/cProfile.py", line 140, in runctx
exec cmd in globals, locals
  File "", line 1, in 
  File "", line 1, in f
SystemError: error return without exception set
___
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