On 10 August 2012 06:48, "Martin v. Löwis" wrote:
> Actually, there appears to be a glitch in the network setup: it appears
> that connections to localhost are not possible in your zone. The tests
> fail with an assertion
>
> self.assertEqual(cm.exception.errno, errno.ECONNREFUSED)
> AssertionErro
Floris Bruynooghe wrote:
> One more thing that might be interesting, the OpenCSW project provides
> access to their build farm to upstream maintainers. They say
> various/all versions of solaris are available and compilers etc are
> already setup, but I have never tried this out. In case someone
Sent in a private message.
Thanks, it seems to be working fine.
Actually, there appears to be a glitch in the network setup: it appears
that connections to localhost are not possible in your zone. The tests
fail with an assertion
self.assertEqual(cm.exception.errno, errno.ECONNREFUSED)
Assert
Thanks, it seems to be working fine. I triggered a build for 27 and
3.x. I'm assuming other builds will just be triggered automatically
when needed from now on?
Indeed; you have probably seen it happening in the waterfall already.
Thanks for providing that slave.
Regards,
Martin
Hi,
On 8 August 2012 11:30, Stefan Krah wrote:
> Could someone with access to a SPARC machine (perhaps with a modern version
> of Debian-sparc) grab a clone from http://hg.python.org/cpython/ and run
> the test suite?
One more thing that might be interesting, the OpenCSW project provides
access
On 9 August 2012 08:11, Antoine Pitrou wrote:
> Le 09/08/2012 01:26, Floris Bruynooghe a écrit :
>> Also, would it make sense to support OpenCSW more out of the box?
>> Currently we carry some patches for setup.py in order to pick up e.g.
>> sqlite from /opt/csw etc. Would there be an interest in
On 9 August 2012 08:22, "Martin v. Löwis" wrote:
> Am 09.08.12 01:26, schrieb Floris Bruynooghe:
>
>> According to the instructions this
>> is the point where I ask for a slave name and password.
>
>
> Sent in a private message.
Thanks, it seems to be working fine. I triggered a build for 27 and
Am 09.08.12 01:26, schrieb Floris Bruynooghe:
According to the instructions this
is the point where I ask for a slave name and password.
Sent in a private message.
Also, would it make sense to support OpenCSW more out of the box?
Currently we carry some patches for setup.py in order to pick u
Le 09/08/2012 01:26, Floris Bruynooghe a écrit :
What Martin said; SPARC under Linux is probably a hobbyist platform.
Enterprise users of Solaris SPARC systems can still volunteer to provide and
maintain a buildslave.
Is http://wiki.python.org/moin/BuildBot the relevant documentation?
Yes,
On 8 August 2012 18:56, Antoine Pitrou wrote:
> Le 08/08/2012 15:25, "Martin v. Löwis" a écrit :
>
>>
>> Of course, when somebody has access to SPARC hardware, *and* they
>> have some interest that Python 3.3 works on it, they should test it.
>> But testing it as a favor to the community is IMO ir
Le 08/08/2012 15:25, "Martin v. Löwis" a écrit :
Of course, when somebody has access to SPARC hardware, *and* they
have some interest that Python 3.3 works on it, they should test it.
But testing it as a favor to the community is IMO irrelevant now;
that particular community is shrinking rapidly
Could someone with access to a SPARC machine (perhaps with a modern version
of Debian-sparc) grab a clone from http://hg.python.org/cpython/ and run
the test suite?
I'd invoke the "scratch your own itch" principle here. SPARC, these
days, is a "minority platform"; I wouldn't mind deleting all S
12 matches
Mail list logo
