Re: [Python-Dev] Sad status of Python 3.x buildbots

On Fri, 10 Oct 2014 12:08:54 -0400 "R. David Murray" wrote: > On Fri, 10 Oct 2014 18:00:06 +0200, Jesus Cea wrote: > > On 10/10/14 17:56, Chris Angelico wrote: > > > Could I write a little > > > monitor at my end that asks every hour if my buildbots can be seen? > > > > AFAIK maintainers already

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Fri, 10 Oct 2014 18:00:06 +0200, Jesus Cea wrote: > On 10/10/14 17:56, Chris Angelico wrote: > > Could I write a little > > monitor at my end that asks every hour if my buildbots can be seen? > > AFAIK maintainers already get an email if the buildbot vanishes long > enough. I am more intereste

Re: [Python-Dev] Sad status of Python 3.x buildbots

It's https://bugs.python.org/issue19884 On Fri, Oct 10, 2014, at 12:08, R. David Murray wrote: > On Fri, 10 Oct 2014 18:00:06 +0200, Jesus Cea wrote: > > On 10/10/14 17:56, Chris Angelico wrote: > > > Could I write a little > > > monitor at my end that asks every hour if my buildbots can be seen?

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 10/10/14 17:45, Jesus Cea wrote: > Thanks for your patience and for notifying me issues when you suffer them. Another issue is changes that actually breaks buildbots and I don't actually know where to start debugging. For instance, currently:

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 10/10/14 17:56, Chris Angelico wrote: > Could I write a little > monitor at my end that asks every hour if my buildbots can be seen? AFAIK maintainers already get an email if the buildbot vanishes long enough. I am more interested in getting an email when my buildbot is consistently red because

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Sat, Oct 11, 2014 at 2:45 AM, Jesus Cea wrote: > On 03/09/14 02:37, Antoine Pitrou wrote: > >> I'm not sure that's an answer to the problem. What we need is not more >> machines, but dedicated buildbot maintainers. > > I would love to get an email if my buildbots are consistently RED for a > fe

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 03/09/14 02:37, Antoine Pitrou wrote: > I'm not sure that's an answer to the problem. What we need is not more > machines, but dedicated buildbot maintainers. I would love to get an email if my buildbots are consistently RED for a few hours. In the past Antoine, Victor and others pinged me ab

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Wed, Sep 3, 2014 at 2:52 PM, Victor Stinner wrote: > > > ARMv7 3.x: "Read-only file system", Mercurial fails... > > I sent an email to Gregory P. Smith (owner). > For mine, its a case of me not having any monitoring for it. Sending me an email worked. In this case the SSD (a very fast usb3 m

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 8 Sep 2014 04:51, "Antonio Cavallo" wrote: > > Ok, > > I've put everything under the tools directory of the build server for the project home:cavallo71:opt-python-interpreters: > > https://build.opensuse.org/package/show/home:cavallo71:opt-python-interpreters/tools > > To get started you need u

Re: [Python-Dev] Sad status of Python 3.x buildbots

Ok, I've put everything under the tools directory of the build server for the project home:cavallo71:opt-python-interpreters: https://build.opensuse.org/package/show/home:cavallo71:opt-python-interpreters/tools To get started you need using the osc client (it uses the same subversion syntax,

Re: [Python-Dev] Sad status of Python 3.x buildbots

Setting up a repo with the code and cleaning a bit here and there. Over the weekend I can put something useable. Nick Coghlan wrote: On 4 September 2014 18:50, A. Cavallo wrote: Yes there are "details" indeed. But not show stoppers. A prototype can be seen here: http://cclimited.webfactional

Re: [Python-Dev] Sad status of Python 3.x buildbots

And so what would need to be done to rectify this problem? If there are no objections, I would like to resolve this particular point, at least until better people can be found to do so. On Thu, Sep 4, 2014 at 8:50 PM, A. Cavallo wrote: > Yes there are "details" indeed. But not show stoppers. A

Re: [Python-Dev] Sad status of Python 3.x buildbots

> > The limiting factor is generally time - various aspects of the current > system are clumsy, but they work, so unless someone is particularly > keen and willing to work through all the factors that led to the > current setup and propose changes (including at least a rough concept > of how ongoin

Re: [Python-Dev] Sad status of Python 3.x buildbots

Also, have you considered using Travis? It would allow us to add to the configurations, at least generally... On Thu, Sep 4, 2014 at 4:16 PM, Nick Coghlan wrote: > On 4 September 2014 11:07, Antonio Cavallo > wrote: > > I wonder if there is any interest in starting to use the opensuse build >

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 4 September 2014 18:50, A. Cavallo wrote: > Yes there are "details" indeed. But not show stoppers. A prototype can be > seen here: http://cclimited.webfactional.com > The nice bit is testing will be executed in a total fresh instance, an added > bonus Oh, very nice! What is needed to get that

Re: [Python-Dev] Sad status of Python 3.x buildbots

Yes there are "details" indeed. But not show stoppers. A prototype can be seen here: http://cclimited.webfactional.com The nice bit is testing will be executed in a total fresh instance, an added bonus On 4 September 2014 05:16:01 GMT+01:00, Nick Coghlan wrote: >On 4 September 2014 11:07, Ant

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 4 September 2014 16:59, Shorya Raj wrote: >> The limiting factor is generally time - various aspects of the current >> system are clumsy, but they work, so unless someone is particularly >> keen and willing to work through all the factors that led to the >> current setup and propose changes (in

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 4 September 2014 15:45, Shorya Raj wrote: > Also, have you considered using Travis? It would allow us to add to the > configurations, at least generally... Many SaaS solution assume the use of specific centralised identity providers, which isn't a function we're prepared to outsource (we know

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 4 September 2014 11:07, Antonio Cavallo wrote: > I wonder if there is any interest in starting to use the opensuse build > servers for continuous build and testing on redhat, fedora suse and (I > think) debian: that will solve once for all the maintenance issues on those > platforms (and provid

Re: [Python-Dev] Sad status of Python 3.x buildbots

I wonder if there is any interest in starting to use the opensuse build servers for continuous build and testing on redhat, fedora suse and (I think) debian: that will solve once for all the maintenance issues on those platforms (and provide a reliable build). Regards, Antonio ___

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Thu, Sep 4, 2014 at 3:32 AM, francis wrote: >> does mean a measure of trust in some external entity, or else some >> very careful rules (mainly firewall), which not every coder will know >> about. > > > Just curious, is there a way to mount the infrastructure the oder way > around? One sets a s

Re: [Python-Dev] Sad status of Python 3.x buildbots

2014-09-03 0:13 GMT+02:00 Victor Stinner : > AMD64 OpenIndiana 3.x: a lot of tests fail with OSError(12, "Not > enough space") or MemoryError. It's probably on issue on the host. > > x86 OpenIndiana 3.x: MemoryError. TestReadline.test_init() also fails. I sent an email to Jesus Cea (owner of these

Re: [Python-Dev] Sad status of Python 3.x buildbots

[...] But it does mean a measure of trust in some external entity, or else some very careful rules (mainly firewall), which not every coder will know about. Just curious, is there a way to mount the infrastructure the oder way around? One sets a system polling for sources changes, if so it st

Re: [Python-Dev] Sad status of Python 3.x buildbots

As mentioned, I don't mind sysadmining a bit, if required. My primary joy would be helping code python, but can't seem to figure out the ideal place to start doing so. Therefore, helping out as sysadmin would be a good start. On Wed, Sep 3, 2014 at 4:58 PM, Cameron Simpson wrote: > On 03Sep2014

Re: [Python-Dev] Sad status of Python 3.x buildbots

Hi all I am using buildbot now for some time and i would be willing to contribute on that. I had small work on openstack buildbot slave but had not the proper infrastructure to get more value out of it. I like that project and automation. Anyway, if i could be of help let me know (; Short to my

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 03Sep2014 11:47, Stephen J. Turnbull wrote: Nick Coghlan writes: > Sorry, I haven't been a very good maintainer for that buildbot (the main > reason it never graduated to the "stable" list). If you send me your public > SSH key, I can add it (I think - if not, I can ask Luke to do it). > Alte

Re: [Python-Dev] Sad status of Python 3.x buildbots

Hello all I don't mind helping out with maintaining buildbots / other build machines. Although I don't have a lot of experience with this sort of thing (I usually just ran a Jenkins for my own work), I think it would be a useful way to contribute. Let me know what I should do if you are all fine wi

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Wed, Sep 3, 2014 at 12:47 PM, Stephen J. Turnbull wrote: > Nick Coghlan writes: > > > Sorry, I haven't been a very good maintainer for that buildbot (the main > > reason it never graduated to the "stable" list). If you send me your public > > SSH key, I can add it (I think - if not, I can as

Re: [Python-Dev] Sad status of Python 3.x buildbots

Nick Coghlan writes: > Sorry, I haven't been a very good maintainer for that buildbot (the main > reason it never graduated to the "stable" list). If you send me your public > SSH key, I can add it (I think - if not, I can ask Luke to do it). > Alternatively, CentOS 6 may exhibit the same prob

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Wed, 3 Sep 2014 08:53:51 +1000 Nick Coghlan wrote: > On 3 Sep 2014 08:15, "Victor Stinner" wrote: > > > > x86 RHEL 6 3.x: TestReadline.test_init() fails, issue #19884. I don't > > have to this platform, I don't know how to fix it. > > Sorry, I haven't been a very good maintainer for that buil

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Wed, 3 Sep 2014 00:13:22 +0200 Victor Stinner wrote: > > AMD64 Snow Leop 3.x: many tests are not reliable (stable) on this > platform. For example, test_logging.test_race() sometimes fail with > PermissionError(1, "Operation not permitted: > '/tmp/test_logging-3-bjulw8iz.log'"). Another exampl

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 03Sep2014 00:13, Victor Stinner wrote: AMD64 Snow Leop 3.x: many tests are not reliable (stable) on this platform. For example, test_logging.test_race() sometimes fail with PermissionError(1, "Operation not permitted: '/tmp/test_logging-3-bjulw8iz.log'"). Another example, test_asyncio.test_st

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 3 Sep 2014 09:00, "Brian Curtin" wrote: > > On Tue, Sep 2, 2014 at 5:53 PM, Nick Coghlan wrote: >> >> From a completely different perspective, does anyone have experience with using BuildBot with OpenStack hosted clients? We may be able to take advantage of the PSF's new(ish) Rackspace infrast

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Tue, Sep 2, 2014 at 5:53 PM, Nick Coghlan wrote: > > On 3 Sep 2014 08:15, "Victor Stinner" wrote: > > > > x86 RHEL 6 3.x: TestReadline.test_init() fails, issue #19884. I don't > > have to this platform, I don't know how to fix it. > > Sorry, I haven't been a very good maintainer for that buil

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 3 Sep 2014 08:15, "Victor Stinner" wrote: > > x86 RHEL 6 3.x: TestReadline.test_init() fails, issue #19884. I don't > have to this platform, I don't know how to fix it. Sorry, I haven't been a very good maintainer for that buildbot (the main reason it never graduated to the "stable" list). If