Thanks for all of this, Victor!
On Fri, Aug 18, 2017, 09:38 Victor Stinner wrote:
> Hi,
>
> Here is a quick report of what changed recently on buildbots.
>
>
> == pythoninfo ==
>
> I added a new "python3 -m test.pythoninfo" command which is now run on
> Travis CI, AppVeyor and buildbots.
>
>
2017-06-29 17:09 GMT+02:00 Victor Stinner :
> Correct me if I'm wrong, but, for the first time, *all reference
> leaks* have been fixed on *all branches* (2.7, 3.5, 3.6 and master),
> on *Linux and Windows*! Before, we mostly focused on the master branch
> (called "default" in Mercurial) on Linux.
On 6/29/2017 5:34 PM, Rob Boehne wrote:
Hello,
I¹m new to the list, and contributing to Python specifically, and I¹m
interested in getting master and 3.6 branches building and working
³better² on UNIX.
I¹ve been looking at a problem building 3.6 on HP-UX and see a PR was
merged into master, http
Hello,
I¹m new to the list, and contributing to Python specifically, and I¹m
interested in getting master and 3.6 branches building and working
³better² on UNIX.
I¹ve been looking at a problem building 3.6 on HP-UX and see a PR was
merged into master, https://github.com/python/cpython/pull/1351 an
2017-06-29 19:13 GMT+02:00 Terry Reedy :
> How about compiler warnings (and errors)?
That would be nice to have, but I don't have the bandwidth to handle this goal.
> When I compile on Windows, there
> are a boatload of orange-yellow warnings. Some are about using a deprecated
> featured; some
On 29Jun2017 1157, Terry Reedy wrote:
On 6/29/2017 1:54 PM, Steve Dower wrote:
Some warnings are also complicated because of the nature of CPython.
For example, the socket module exposes deprecated CRT functions (on
Windows) directly because the API of the socket module promises to
provide the
On 6/29/2017 1:54 PM, Steve Dower wrote:
On 29Jun2017 1013, Terry Reedy wrote:
Great work.
Agreed. Thanks, Victor!
How about compiler warnings (and errors)? When I compile on Windows,
there are a boatload of orange-yellow warnings. Some are about using
a deprecated featured; some about do
On 29Jun2017 1013, Terry Reedy wrote:
Great work.
Agreed. Thanks, Victor!
How about compiler warnings (and errors)? When I compile on Windows,
there are a boatload of orange-yellow warnings. Some are about using a
deprecated featured; some about dodgy casts; some (I presume) about
other t
On 6/29/2017 11:09 AM, Victor Stinner wrote:
Hi,
Our buildbots are now even more stable than in my previous buildbot report.
Many random failures have been fixed, even if there are still many
rare random failures (most of them are related to multiprocessing).
Search for issues created by "hayp
On Thu, Jan 28, 2016 at 9:41 PM, Chris Angelico wrote:
> However, as I was doing so (and I just discarded a draft message where
> I'd been typing up notes), my entire system went kerblooie, and I've
> spent the last day rebuilding stuff from scratch. When I get around to
> it, I'll rebuild the bui
On Thu, Jan 28, 2016 at 7:35 PM, Martin Panter wrote:
> Other things that come to mind are to see if there is anything odd
> about the buildbot’s Linux kernel and glibc versions. Maybe run the
> Python script under “strace” to see if anything strange is going on.
>
I did that, and a few other thi
> After digging through test_socket.py for over an hour (the MRO for
> RecvmsgUDP6Test is enormous!!), I've boiled the issue down to this:
>
> import socket
> MSG = b'asdf qwer zxcv'
> serv = socket.socket(socket.AF_INET6, socket.SOCK_DGRAM)
> serv.bind(("::1", 0))
> cli = socket.socket(socket.AF_I
On Wed, Jan 27, 2016 at 8:39 PM, Victor Stinner
wrote:
> 2016-01-23 7:03 GMT+01:00 Chris Angelico :
>> Running just that test file:
>>
>> $ ./python Lib/test/test_socket.py
>> ... chomp lots of lines ...
>> testRecvmsgPeek (__main__.RecvmsgUDP6Test) ...
>>
>> seems to indicate that the stall is du
2016-01-23 7:03 GMT+01:00 Chris Angelico :
> I just had a major crash on the system that hosts the
> angelico-debian-amd64 buildbot, and as usual, checked it carefully
> after bringing everything up. It seems now to be timing out after an
> hour of operation:
>
> http://buildbot.python.org/all/buil
On Sun, Jan 24, 2016 at 1:37 AM, Victor Stinner
wrote:
> 3600 seconds is the maximum duration of a single test file. We may reduce it
> since a single test file should not take longer than 30 min. Maybe we can do
> better and put the timeout on a single test function.
I'd be inclined to put some
3600 seconds is the maximum duration of a single test file. We may reduce
it since a single test file should not take longer than 30 min. Maybe we
can do better and put the timeout on a single test function.
Victor
___
Python-Dev mailing list
Python-Dev@
On Sat, Jan 23, 2016 at 5:39 PM, Zachary Ware
wrote:
> On Sat, Jan 23, 2016 at 12:03 AM, Chris Angelico wrote:
>> By the way, this looks odd:
>>
>> make buildbottest TESTOPTS= TESTPYTHONOPTS= TESTTIMEOUT=3600
>> in dir /root/buildarea/3.x.angelico-debian-amd64/build (timeout 3900 secs)
>>
>> The
On Sat, Jan 23, 2016 at 12:03 AM, Chris Angelico wrote:
> By the way, this looks odd:
>
> make buildbottest TESTOPTS= TESTPYTHONOPTS= TESTTIMEOUT=3600
> in dir /root/buildarea/3.x.angelico-debian-amd64/build (timeout 3900 secs)
>
> The parameter says 3600 (which corresponds to the error message a
python-dev@python.org>
Subject: Re: [Python-Dev] Buildbot x86 XP-4 3.x doesn't compile anymore: drop
it?
Le 28 mars 2015 21:15, "David Bolen"
mailto:db3l@gmail.com>> a écrit :
> I'm assuming you aren't suggesting turning off the XP buildbot
> entirely,
Le 28 mars 2015 21:15, "David Bolen" a écrit :
> I'm assuming you aren't suggesting turning off the XP buildbot
> entirely, correct?
I'm talking about the 3.x slave, so only python 3.5.
Would it be possible to specify in What's New In Python 3.5 which Windows
versions are no more supported?
Vi
Victor Stinner writes:
> Would it be possible to fix this buildbot, or to turn it off?
(...)
> By the way, do we seriously want to support Windows XP? I mean, *who*
> will maintain it (no me sorry!). I saw recent changes to explicitly
> *drop* support for Windows older than Visa (stop using GetT
On Sat, Mar 28, 2015 at 5:57 AM, Victor Stinner
wrote:
> Hi,
>
> There are many failures on the AIX buildbot. Can someone try to fix
> them? Or would it be possible to turn off the buildbot to quickly see
> regressions?
>
> http://buildbot.python.org/all/builders/PPC64%20AIX%203.x/builds/3426/step
Le samedi 28 mars 2015, Tim Golden a écrit :
>
> For myself I'm quite willing for someone to ping me with: "there's a
> Windows buildbot gone red; can you have a look?" But I have precious little
> time, and if the failure requires me to garner an understanding of a
> deep-level code change, a ver
On 28/03/2015 09:51, Victor Stinner wrote:
Hi,
The buildbot x86 XP-4 3.x doesn't compile anymore since 3 months or
more (maybe when Steve upgraded the Visual Studio project to VS 2015?
I don't know).
Would it be possible to fix this buildbot, or to turn it off?
By the way, do we seriously want
On Thu, Jan 2, 2014 at 9:17 AM, "Martin v. Löwis" wrote:
> So it should be able to handle a failover from one link to
> the other, but it's certainly better to bind it to the more
> reliable transport. I believe you can somehow configure the
> frequency of ping messages so that you network doesn't
Am 31.12.13 01:24, schrieb Chris Angelico:
> Does Buildbot retain a constant TCP socket to its server?
In short: yes. A little bit longer: It uses the Twisted
PerspectiveBroker protocol. That has nearly-transparent
reconnects (but as your case shows, not fully transparent),
and does regular ping
On Tue, Dec 31, 2013 at 12:35 PM, Zach Ware
wrote:
>>Debian Wheezy doesn't package 3.3 but only 3.2, so I grabbed 3.2's
>>build-deps. They're now installed, so the next build should have
>>everything for that. Does anyone happen to know what (if anything) 3.3
>>needs that 3.2 doesn't?
>
> You'll n
Chris Angelico wrote:
>On Tue, Dec 31, 2013 at 5:18 AM, Christian Heimes
> wrote:
>> The buildbot is missing some vital header files. Please run:
>>
>> # apt-get build-dep python3.3
>>
>> to install all required dependencies.
>
>Debian Wheezy doesn't package 3.3 but only 3.2, so I grabbed 3.2'
On Tue, Dec 31, 2013 at 11:42 AM, Antoine Pitrou wrote:
> On Tue, 31 Dec 2013 11:24:26 +1100
> Chris Angelico wrote:
>> Does Buildbot retain a constant TCP socket to its server? I'm seeing this:
>>
>> http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.3/builds/0
>
> I'm quite sure
On Tue, 31 Dec 2013 11:24:26 +1100
Chris Angelico wrote:
> Does Buildbot retain a constant TCP socket to its server? I'm seeing this:
>
> http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.3/builds/0
I'm quite sure it does. It's necessary to get a real-time view of the
test log.
On Tue, Dec 31, 2013 at 5:18 AM, Christian Heimes wrote:
> The buildbot is missing some vital header files. Please run:
>
> # apt-get build-dep python3.3
>
> to install all required dependencies.
Debian Wheezy doesn't package 3.3 but only 3.2, so I grabbed 3.2's
build-deps. They're now installe
On Mon, 30 Dec 2013 15:00:02 -0600, Zachary Ware
wrote:
> On Mon, Dec 30, 2013 at 2:31 PM, Zachary Ware
> wrote:
> > and we should just fix the tests that expect zlib unconditionally.
>
> Both of which turned out to be trivial; the import of zlib was already
> guarded in both places, but one sk
On Mon, Dec 30, 2013 at 2:31 PM, Zachary Ware
wrote:
> and we should just fix the tests that expect zlib unconditionally.
Both of which turned out to be trivial; the import of zlib was already
guarded in both places, but one skip was checking the wrong name and
the other just didn't try to skip,
On Mon, Dec 30, 2013 at 12:18 PM, Christian Heimes wrote:
> Am 30.12.2013 15:02, schrieb Chris Angelico:
>> On Tue, Dec 31, 2013 at 12:05 AM, Chris Angelico wrote:
>>> On Sun, Dec 8, 2013 at 12:35 AM, Chris Angelico wrote:
In another thread it was suggested that a new buildbot running as ro
Am 30.12.2013 15:02, schrieb Chris Angelico:
> On Tue, Dec 31, 2013 at 12:05 AM, Chris Angelico wrote:
>> On Sun, Dec 8, 2013 at 12:35 AM, Chris Angelico wrote:
>>> In another thread it was suggested that a new buildbot running as root
>>> would be of value. I've spun up a virtual machine running
On Tue, Dec 31, 2013 at 12:05 AM, Chris Angelico wrote:
> On Sun, Dec 8, 2013 at 12:35 AM, Chris Angelico wrote:
>> In another thread it was suggested that a new buildbot running as root
>> would be of value. I've spun up a virtual machine running Debian
>> Wheezy amd64, have installed buildbot f
On Sun, Dec 8, 2013 at 12:35 AM, Chris Angelico wrote:
> In another thread it was suggested that a new buildbot running as root
> would be of value. I've spun up a virtual machine running Debian
> Wheezy amd64, have installed buildbot from the repository (version
> 0.8.6p1), and am ready to have i
On Sat, 10 Aug 2013 20:25:04 -0400
Terry Reedy wrote:
> At least the following 3.4 buildbots have failed today with an error I
> do not understand: AMD64 FreeBSD, PPC64, x86Ubuntu, x86 WinServer 2003.
http://bugs.python.org/issue18706
___
Python-Dev
Just as an FYI, we set up a new "optimized" Snakebite slave
yesterday on the Mac OS X Mountain Lion box. I also set up
remote access to that box in the process -- you can connect
to it via the ~/.snakebite/sb 'x8' alias.
(That box happens to be the fastest (and most contempora
On Wed, Sep 26, 2012 at 04:13:42PM -0700, Benjamin Peterson wrote:
> 2012/9/26 Maciej Fijalkowski :
> > On Thu, Sep 27, 2012 at 1:00 AM, Benjamin Peterson
> > wrote:
> >> In light of issue #16046, I think it would be helpful to have a
> >> buildbot running the testsuite with -O enabled.
> >
> > H
2012/9/26 Maciej Fijalkowski :
> On Thu, Sep 27, 2012 at 1:00 AM, Benjamin Peterson
> wrote:
>> In light of issue #16046, I think it would be helpful to have a
>> buildbot running the testsuite with -O enabled.
>
> How about deprecating -O completely instead? It does not seem to give
> any speedu
On Wed, 26 Sep 2012 19:00:53 -0400, Benjamin Peterson
wrote:
> In light of issue #16046, I think it would be helpful to have a
> buildbot running the testsuite with -O enabled.
I've got some (slow) hardware I could dedicate to this, though
it may take me a few weeks to find time to set it up.
-
On Thu, Sep 27, 2012 at 1:00 AM, Benjamin Peterson wrote:
> In light of issue #16046, I think it would be helpful to have a
> buildbot running the testsuite with -O enabled.
How about deprecating -O completely instead? It does not seem to give
any speedups and definitely gives headaches.
Brian Curtin, 03.11.2011 15:59:
On Sat, Oct 22, 2011 at 14:30, Andrea Crotti wrote:
On 10/21/2011 10:08 PM, Antoine Pitrou wrote:
Hello,
There are currently a bunch of various buildbot failures on all 3
branches. I would remind committers to regularly take a look at the
buildbots, so that the
On Sat, Oct 22, 2011 at 14:30, Andrea Crotti wrote:
> On 10/21/2011 10:08 PM, Antoine Pitrou wrote:
>>
>> Hello,
>>
>> There are currently a bunch of various buildbot failures on all 3
>> branches. I would remind committers to regularly take a look at the
>> buildbots, so that these failures get s
On Sun, Oct 23, 2011 at 5:30 AM, Andrea Crotti
wrote:
> If one is not clearly defined, maybe notifying the last N developers that
> committed
> between the last successful builds and the failing build, would it be
> possible and make sense?
Yeah, as Antoine noted, that's where we want to get to e
On Sat, 22 Oct 2011 20:30:34 +0100
Andrea Crotti wrote:
>
> In my previous workplace if someone broke a build committing something
> wrong he/she
> had to bring cake for everyone next meeting.
>
> The cake is not really feasible I guess, but isn't it possible to notify
> the developer that
>
On 10/21/2011 10:08 PM, Antoine Pitrou wrote:
Hello,
There are currently a bunch of various buildbot failures on all 3
branches. I would remind committers to regularly take a look at the
buildbots, so that these failures get solved reasonably fast.
Regards
Antoine.
In my previous workplace i
Le 20/08/2011 22:52, Paul Moore a écrit :
> My buildbot seems to have been failing for a while (I've been away on
> holiday) - http://www.python.org/dev/buildbot/buildslaves/moore-windows
>
> The failures seem to generally be in distutils and/or packaging. I see
> quite a lot of reds in the waterf
On Tue, Apr 5, 2011 at 09:05, Antoine Pitrou wrote:
>
> Hello,
>
> For the record, we have 9 stable buildbots, one of which is currently
> offline: 3 Windows, 2 OS X, 3 Linux and 1 Solaris.
> Paul Moore's XP buildbot is back in the stable stable.
> (http://www.python.org/dev/buildbot/all/waterfal
On Thu, Apr 7, 2011 at 12:01 AM, Antoine Pitrou wrote:
> Le mercredi 06 avril 2011 à 23:55 +1000, Nick Coghlan a écrit :
>> Since it appears the intermittent failures affecting these platforms
>> have been dealt with, is it time to switch python-committers email
>> notifications back on for buildb
Le mercredi 06 avril 2011 à 23:55 +1000, Nick Coghlan a écrit :
> On Wed, Apr 6, 2011 at 12:05 AM, Antoine Pitrou wrote:
> >
> > Hello,
> >
> > For the record, we have 9 stable buildbots, one of which is currently
> > offline: 3 Windows, 2 OS X, 3 Linux and 1 Solaris.
> > Paul Moore's XP buildbot
On Wed, Apr 6, 2011 at 12:05 AM, Antoine Pitrou wrote:
>
> Hello,
>
> For the record, we have 9 stable buildbots, one of which is currently
> offline: 3 Windows, 2 OS X, 3 Linux and 1 Solaris.
> Paul Moore's XP buildbot is back in the stable stable.
> (http://www.python.org/dev/buildbot/all/waterf
On Sun, Mar 20, 2011 at 9:44 AM, David Bolen wrote:
> Nick Coghlan writes:
>
>> I don't want to give up completely on the idea just yet, but I'll
>> experiment in the sandbox before I turn it back on.
>
> If you get to that point again, I'd also be willing to pick a time to
> manually check out t
Nick Coghlan writes:
> I don't want to give up completely on the idea just yet, but I'll
> experiment in the sandbox before I turn it back on.
If you get to that point again, I'd also be willing to pick a time to
manually check out the right branch or whatever and try it manually
on one of two o
On Sun, Mar 20, 2011 at 5:52 AM, Antoine Pitrou wrote:
>> I suspect, however, that as soon as something else commits to the 3.x
>> branch and causes a new test, that test_crashers (presumably from
>> changeset 9c6dcb5d8f01) will likely just take the slaves down again.
>
> The test is already disab
On Sat, 19 Mar 2011 15:41:51 -0400
David Bolen wrote:
>
> Thanks. Is that a single button somewhere or do I need to cancel the
> pending builds individually when there are several waiting?
There seems to be a single button.
> In any event it looks like the retries of the failing 3.x build
> st
Antoine Pitrou writes:
> I've enabled the button to cancel pending builds in the Web UI. You
> should be able to bring back the Ubuntu slave online. You can do the
> same (cancel pending builds) for other slaves if needed.
Thanks. Is that a single button somewhere or do I need to cancel the
pen
On Sat, 19 Mar 2011 14:45:10 -0400
David Bolen wrote:
>
> The problem is that the failing build is automatically retried when I
> try to reconnect the buildbot, so it just get rights into trouble
> again. The comment in that build's changeset looks like it might be
> getting rolled back?
>
> As
Am 13.11.2010 14:00, schrieb Mark Dickinson:
> On Fri, Nov 12, 2010 at 9:29 AM, "Martin v. Löwis" wrote:
>> As you may have noticed: I updated the buildbot master to release 0.8.2.
>> If you notice any problems, please post them here.
>
> One effect of this change seems to be that bbreport[1] no
On Fri, Nov 12, 2010 at 9:29 AM, "Martin v. Löwis" wrote:
> As you may have noticed: I updated the buildbot master to release 0.8.2.
> If you notice any problems, please post them here.
One effect of this change seems to be that bbreport[1] no longer
works, since it appears that buildbot 0.8.2 ha
On Fri, 12 Nov 2010 20:53:00 +0100
"Martin v. Löwis" wrote:
> > Thanks Martin, for all you do to keep our infrastructure humming along
> > smoothly, including the recent Roundup migration.
>
> I just write the announcements :-) In this case. thanks should also
> extend to Izak Burger of Upfront H
> Thanks Martin, for all you do to keep our infrastructure humming along
> smoothly, including the recent Roundup migration.
I just write the announcements :-) In this case. thanks should also
extend to Izak Burger of Upfront Hosting who did most of the setup
(I just did the DNS changes), and to b
On 12 November 2010 16:15, Barry Warsaw wrote:
> On Nov 12, 2010, at 10:29 AM, Martin v. Löwis wrote:
>
>>As you may have noticed: I updated the buildbot master to release 0.8.2.
>>If you notice any problems, please post them here.
>
> Pretty! My buildbot seems fine.
Yes, I like the new look.
>
On Nov 12, 2010, at 10:29 AM, Martin v. Löwis wrote:
>As you may have noticed: I updated the buildbot master to release 0.8.2.
>If you notice any problems, please post them here.
Pretty! My buildbot seems fine.
>Slave operators can upgrade their installations at their own pace;
>buildbot is hig
On 05:50 pm, solip...@pitrou.net wrote:
Le lundi 08 novembre 2010 � 18:46 +0100, S�bastien Sabl� a �crit :
xlc: 1501-216 (W) command option - -qmaxmem=18000 is not recognized -
passed to ld
Is -qmaxmem really necessary to build Python?
If so, you could try passing it in CFLAGS.
However running
Hi Antoine,
I tried to provide command lines arguments to configure instead of
environment variables with:
configureFlags = ["--with-pydebug", "--without-computed-gotos",
"CC=xlc", 'OPT="-O2 -qmaxmem=18000"']
But that would fail: on the slave, configure would run like that:
./configure --wi
On Mon, Nov 08, 2010 at 06:50:32PM +0100, Antoine Pitrou wrote:
> > However running 2 different slaves per host in order to distinguish xlc
> > and gcc would be OK; though I would appreciate if they could run
> > sequentially rather than in parallel as that would limit the host load.
>
> If ther
Le lundi 08 novembre 2010 à 18:46 +0100, Sébastien Sablé a écrit :
> xlc: 1501-216 (W) command option - -qmaxmem=18000 is not recognized -
> passed to ld
Is -qmaxmem really necessary to build Python?
If so, you could try passing it in CFLAGS.
> However running 2 different slaves per host in orde
On Fri, 15 Oct 2010 17:38:47 +0200
Sébastien Sablé wrote:
>
> Could you please take a look at those modifications in master.cfg,
> provide me some password for the bot slaves and apply the corrections in
> those issues?
About the master.cfg modifications: there should be no need for
separate e
> I got no reply concerning those modifications to the buildbot script so
> that I could run 2 slaves on AIX.
I'm really really reluctant here. The proposed/requested changes are
fairly intrusive, even though AIX is just a minority platform. So I need
to find some time to rewrite them, which I hav
Hi Martin,
I got no reply concerning those modifications to the buildbot script so
that I could run 2 slaves on AIX.
I am able to spend some time at the moment on Python for AIX because we
are migrating the product in my company from AIX 5.3 to AIX 6.1.
However once this is done, by the end o
Hi Sridhar,
Le 15/10/2010 18:50, Sridhar Ratnakumar a écrit :
We definitely like to share our core Python patches for AIX 5.1/5.2 and other
platforms.
Great to hear that ActiveState shares their improvements for Python on
AIX! Thanks for the patch in git, I will check it and try to open some
On Fri, 15 Oct 2010 17:38:47 +0200, =?UTF-8?B?U8OpYmFzdGllbiBTYWJsw6k=?=
wrote:
> I finally got the authorization to run some buildbot slaves on our AIX
> servers.
>
> I made some tests with a buildbot script as close as possible to what
> you already use. Here is a patch that show the kind of
On 2010-09-20, at 7:41 AM, Sébastien Sablé wrote:
> Le 17/09/2010 15:05, Antoine Pitrou a écrit :
>> Following on Martin's comments, you might also want to share things
>> with the ActiveState guys who, AFAIK, maintain an AIX version of Python
>> (but you have been the most active AIX user on the
Hi Martin,
I finally got the authorization to run some buildbot slaves on our AIX
servers.
I made some tests with a buildbot script as close as possible to what
you already use. Here is a patch that show the kind of modifications I
had to do in order to get the buildbot slave to correctly ru
> Also could you provide me the master.cfg file (with obfuscated
> passwords) that is used by the Python buildbot master or tell me if it
> is in subversion somewhere?
Attached!
Regards,
Martin
# -*- python -*-
# This is a sample buildmaster config file. It must be installed as
# 'master.cfg' in
> A workaround is to just put them in the /etc/hosts file.
That doesn't really help: the test suite also relies on a number of host
names.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
Martin v. Löwis wrote:
> That's a common OSX problem/bug. Processes occasionally lose the ability
> to resolve host names. Various theories float around what's causing this
> (most commonly, people expect that a "controlling terminal" must be
> present); my theory is this:
>
> There is a Mach po
Martin v. Löwis wrote:
> Bill Janssen wrote:
> > parc-leopard-1 (and most of the other builders) are failing the svn
> > checkout with the following error:
> >
> > svn: PROPFIND of '/projects/python/trunk': Could not resolve hostname
> > `svn.python.org': Temporary failure in name resolution
>
Bill Janssen wrote:
> parc-leopard-1 (and most of the other builders) are failing the svn
> checkout with the following error:
>
> svn: PROPFIND of '/projects/python/trunk': Could not resolve hostname
> `svn.python.org': Temporary failure in name resolution
> (http://svn.python.org)
>
> When I l
> How about:
> "indicates that related test failures are causing buildbot
> instability"
Ok, changed!
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.or
> Well the general situation would be slightly easier to appreciate if there
> was a
> public medium where buildbot info was exchanged, announcements done, and
> problems tracked. Some kind of tracker, tracker keyword, mailing-list, or
> anything else.
As for the tracker keyword - I created one (
twistedmatrix.com> writes:
>
> Is your idea that this would be for tracking issues with the *bots*
> themselves? That is, not just for tracking cases where some test method
> fails on a particular bot, but for tracking cases where, say, a bot's
> host has run out of disk space and cannot run
On Fri, 30 Oct 2009 at 09:57, "Martin v. L?wis" wrote:
But the real reason for having a buildbot category (or at least a keyword)
would be to be able to tag all bugs that are currently making buildbots
fail that are _not_ the result of a recent checkin. This would make
the task of finding the bu
On Fri, Oct 30, 2009 at 10:15 AM, wrote:
> On 12:55 pm, jnol...@gmail.com wrote:
>>
>> On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. Löwis"
>> wrote:
>>>
>>> I'm confused: first you said they fail, now you say they get skipped.
>>> Which one is it? I agree with R. David's analysis: if they fail, i
On Fri, 30 Oct 2009 at 08:55, Jesse Noller wrote:
On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. L?wis" wrote:
I'm confused: first you said they fail, now you say they get skipped.
Which one is it? I agree with R. David's analysis: if they fail, it's
a multiprocessing bug, if they get skipped, it'
On 12:55 pm, jnol...@gmail.com wrote:
On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. Löwis"
wrote:
I'm confused: first you said they fail, now you say they get skipped.
Which one is it? I agree with R. David's analysis: if they fail, it's
a multiprocessing bug, if they get skipped, it's a flaw in
On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. Löwis" wrote:
> I'm confused: first you said they fail, now you say they get skipped.
> Which one is it? I agree with R. David's analysis: if they fail, it's
> a multiprocessing bug, if they get skipped, it's a flaw in the build
> slave configuration (b
> But the real reason for having a buildbot category (or at least a keyword)
> would be to be able to tag all bugs that are currently making buildbots
> fail that are _not_ the result of a recent checkin. This would make
> the task of finding the bugs that need to be cleaned up to stabilize
> the
Jesse Noller wrote:
> On Thu, Oct 29, 2009 at 8:31 PM, R. David Murray
> wrote:
>
>> I'd say that particular one is a bug in the tests. If /dev/shm is
>> not available and is required, then the tests should be skipped with
>> an appropriate message. It would also secondarily be an issue with
>
On Thu, Oct 29, 2009 at 8:31 PM, R. David Murray wrote:
> I'd say that particular one is a bug in the tests. If /dev/shm is
> not available and is required, then the tests should be skipped with
> an appropriate message. It would also secondarily be an issue with
> the buildbot fleet, since mul
On 29 Oct, 11:41 pm, jnol...@gmail.com wrote:
On Thu, Oct 29, 2009 at 7:04 PM, wrote:
On 02:30 pm, solip...@pitrou.net wrote:
Hello,
What do you think of creating a "buildbot" category in the tracker?
There
are
often problems on specific buildbots which would be nice to track,
but
there
On Thu, 29 Oct 2009 at 19:41, Jesse Noller wrote:
Then again, I know for a fact certain tests fail ONLY on certain
buildbots because of the way they're configured. For example, certain
multiprocessing tests will fail if /dev/shm isn't accessible on Linux,
and several of the buildbosts are in tigh
On Thu, Oct 29, 2009 at 7:04 PM, wrote:
> On 02:30 pm, solip...@pitrou.net wrote:
>>
>> Hello,
>>
>> What do you think of creating a "buildbot" category in the tracker? There
>> are
>> often problems on specific buildbots which would be nice to track, but
>> there's
>> nowhere to do so.
>
> Is yo
On 02:30 pm, solip...@pitrou.net wrote:
Hello,
What do you think of creating a "buildbot" category in the tracker?
There are
often problems on specific buildbots which would be nice to track, but
there's
nowhere to do so.
Is your idea that this would be for tracking issues with the *bots*
> What do you think of creating a "buildbot" category in the tracker? There are
> often problems on specific buildbots which would be nice to track, but there's
> nowhere to do so.
Do you have any specific reports that you would want to classify with
this category?
Regards,
Martin
___
On Fri, May 29, 2009 at 12:39 AM, David Bolen wrote:
> David Bolen writes:
>
>> Ooops, that's mine. Geez - it's a VM, but has a 10GB C: drive, and
>> the actual build slave has its working directory on a separate virtual
>> drive. Wonder what the heck has filled up the system drive. I'm
>> wor
David Bolen writes:
> Ooops, that's mine. Geez - it's a VM, but has a 10GB C: drive, and
> the actual build slave has its working directory on a separate virtual
> drive. Wonder what the heck has filled up the system drive. I'm
> working on it now though.
Well, looks like it was 5+GB of tempo
Tarek Ziadé writes:
> - x86 XP-4 (trunk and 3x) is throwing an "no space left on device"
> error when it compiles the sqlite module in its temp dir
Ooops, that's mine. Geez - it's a VM, but has a 10GB C: drive, and
the actual build slave has its working directory on a separate virtual
drive. W
1 - 100 of 236 matches
Mail list logo
