From vstinner at redhat.com  Wed Apr  3 10:25:55 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Wed, 3 Apr 2019 16:25:55 +0200
Subject: [Python-buildbots] Adding a Fedora Rawhide x86_64 to the
 buildbot fleet
In-Reply-To: <CAKJDb-MkVrowsxpM0nkDPBf7B0gh95D7s48ChPoo5ibj04+O8w@mail.gmail.com>
References: <791621877.6131904.1551710429204.JavaMail.zimbra@redhat.com>
 <2079274997.6136374.1551711320334.JavaMail.zimbra@redhat.com>
 <CAKJDb-MkVrowsxpM0nkDPBf7B0gh95D7s48ChPoo5ibj04+O8w@mail.gmail.com>
Message-ID: <CA+3bQGGHgC1eQCJg+9mf2OAQc=Vp-YVd6eG0foJzpUFDDBXrxQ@mail.gmail.com>

I merged https://github.com/python/buildmaster-config/pull/85 to add
the new "AMD64 Fedora Rawhide" jobs on "cstratak-fedora" worker ;-)

Victor

Le sam. 30 mars 2019 ? 17:37, Zachary Ware
<zachary.ware+pydev at gmail.com> a ?crit :
> You can expect an email from me shortly with your worker name and
> password.  Once you have that you'll be able to connect your worker,
> but it won't actually do anything until we assign builders to it which
> we can do via a PR to the https://github.com/python/buildmaster-config
> repository, which houses the non-secret configuration for the buildbot
> master.
>
> Thanks for setting up a worker!
> --
> Zach
> _______________________________________________
> Python-Buildbots mailing list
> Python-Buildbots at python.org
> https://mail.python.org/mailman/listinfo/python-buildbots



-- 
Night gathers, and now my watch begins. It shall not end until my death.

From cstratak at redhat.com  Sun Apr  7 21:10:43 2019
From: cstratak at redhat.com (Charalampos Stratakis)
Date: Sun, 7 Apr 2019 21:10:43 -0400 (EDT)
Subject: [Python-buildbots] Adding a Fedora Rawhide x86_64 to the
 buildbot fleet
In-Reply-To: <CA+3bQGGHgC1eQCJg+9mf2OAQc=Vp-YVd6eG0foJzpUFDDBXrxQ@mail.gmail.com>
References: <791621877.6131904.1551710429204.JavaMail.zimbra@redhat.com>
 <2079274997.6136374.1551711320334.JavaMail.zimbra@redhat.com>
 <CAKJDb-MkVrowsxpM0nkDPBf7B0gh95D7s48ChPoo5ibj04+O8w@mail.gmail.com>
 <CA+3bQGGHgC1eQCJg+9mf2OAQc=Vp-YVd6eG0foJzpUFDDBXrxQ@mail.gmail.com>
Message-ID: <1749223224.16516013.1554685843862.JavaMail.zimbra@redhat.com>

Just wanna say thank you to both for helping me setup the worker.

It's up, running and green: https://buildbot.python.org/all/#/workers/32 :)

I'll probably set different types of builds as well soon, as far as the computing power allows it.

And possibly some different architectures in the future, as well.

----- Original Message -----
> From: "Victor Stinner" <vstinner at redhat.com>
> To: "Zachary Ware" <zachary.ware+pydev at gmail.com>
> Cc: "python-buildbo." <python-buildbots at python.org>
> Sent: Wednesday, April 3, 2019 4:25:55 PM
> Subject: Re: [Python-buildbots] Adding a Fedora Rawhide x86_64 to the buildbot fleet
> 
> I merged https://github.com/python/buildmaster-config/pull/85 to add
> the new "AMD64 Fedora Rawhide" jobs on "cstratak-fedora" worker ;-)
> 
> Victor
> 
> Le sam. 30 mars 2019 ? 17:37, Zachary Ware
> <zachary.ware+pydev at gmail.com> a ?crit :
> > You can expect an email from me shortly with your worker name and
> > password.  Once you have that you'll be able to connect your worker,
> > but it won't actually do anything until we assign builders to it which
> > we can do via a PR to the https://github.com/python/buildmaster-config
> > repository, which houses the non-secret configuration for the buildbot
> > master.
> >
> > Thanks for setting up a worker!
> > --
> > Zach
> > _______________________________________________
> > Python-Buildbots mailing list
> > Python-Buildbots at python.org
> > https://mail.python.org/mailman/listinfo/python-buildbots
> 
> 
> 
> --
> Night gathers, and now my watch begins. It shall not end until my death.
> _______________________________________________
> Python-Buildbots mailing list
> Python-Buildbots at python.org
> https://mail.python.org/mailman/listinfo/python-buildbots
> 

-- 
Regards,

Charalampos Stratakis
Software Engineer
Python Maintenance Team, Red Hat

From vstinner at redhat.com  Mon Apr  8 08:15:39 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Mon, 8 Apr 2019 14:15:39 +0200
Subject: [Python-buildbots] Adding a Fedora Rawhide x86_64 to the
 buildbot fleet
In-Reply-To: <1749223224.16516013.1554685843862.JavaMail.zimbra@redhat.com>
References: <791621877.6131904.1551710429204.JavaMail.zimbra@redhat.com>
 <2079274997.6136374.1551711320334.JavaMail.zimbra@redhat.com>
 <CAKJDb-MkVrowsxpM0nkDPBf7B0gh95D7s48ChPoo5ibj04+O8w@mail.gmail.com>
 <CA+3bQGGHgC1eQCJg+9mf2OAQc=Vp-YVd6eG0foJzpUFDDBXrxQ@mail.gmail.com>
 <1749223224.16516013.1554685843862.JavaMail.zimbra@redhat.com>
Message-ID: <CA+3bQGGu0_y9C+3MiOVmxaGBEgGxToh5scE7Jw3O4A5GNe51xQ@mail.gmail.com>

Charalampos and me changed the worker config to run tests using -j10
rather than -j2. It's way faster :-)

-j2: "Total duration: 14 min 30 sec"
-j10: "Total duration: 4 min 13 sec"

Victor

Le lun. 8 avr. 2019 ? 03:10, Charalampos Stratakis
<cstratak at redhat.com> a ?crit :
>
> Just wanna say thank you to both for helping me setup the worker.
>
> It's up, running and green: https://buildbot.python.org/all/#/workers/32 :)
>
> I'll probably set different types of builds as well soon, as far as the computing power allows it.
>
> And possibly some different architectures in the future, as well.
>
> ----- Original Message -----
> > From: "Victor Stinner" <vstinner at redhat.com>
> > To: "Zachary Ware" <zachary.ware+pydev at gmail.com>
> > Cc: "python-buildbo." <python-buildbots at python.org>
> > Sent: Wednesday, April 3, 2019 4:25:55 PM
> > Subject: Re: [Python-buildbots] Adding a Fedora Rawhide x86_64 to the buildbot fleet
> >
> > I merged https://github.com/python/buildmaster-config/pull/85 to add
> > the new "AMD64 Fedora Rawhide" jobs on "cstratak-fedora" worker ;-)
> >
> > Victor
> >
> > Le sam. 30 mars 2019 ? 17:37, Zachary Ware
> > <zachary.ware+pydev at gmail.com> a ?crit :
> > > You can expect an email from me shortly with your worker name and
> > > password.  Once you have that you'll be able to connect your worker,
> > > but it won't actually do anything until we assign builders to it which
> > > we can do via a PR to the https://github.com/python/buildmaster-config
> > > repository, which houses the non-secret configuration for the buildbot
> > > master.
> > >
> > > Thanks for setting up a worker!
> > > --
> > > Zach
> > > _______________________________________________
> > > Python-Buildbots mailing list
> > > Python-Buildbots at python.org
> > > https://mail.python.org/mailman/listinfo/python-buildbots
> >
> >
> >
> > --
> > Night gathers, and now my watch begins. It shall not end until my death.
> > _______________________________________________
> > Python-Buildbots mailing list
> > Python-Buildbots at python.org
> > https://mail.python.org/mailman/listinfo/python-buildbots
> >
>
> --
> Regards,
>
> Charalampos Stratakis
> Software Engineer
> Python Maintenance Team, Red Hat



-- 
Night gathers, and now my watch begins. It shall not end until my death.

From vstinner at redhat.com  Wed Apr 10 19:08:25 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Thu, 11 Apr 2019 01:08:25 +0200
Subject: [Python-buildbots] Disable notifiations on broken workers
Message-ID: <CA+3bQGGtN0jwKuoSD7_AL+2=M-6SvYMGnasv=2B2m6=P3zhBtw@mail.gmail.com>

Hi,

I propose to disable email and IRC notifications on workers which were
never green (tests always failed):
https://github.com/python/buildmaster-config/pull/86

* Alpine Linux
* Cygwin
* "AMD64 Clang UBSan 3." (3.6, 3.7 and 3.x, surprisingly, 2.7 is green)

Does anyone have a good reason to keep notifications for these workers?

I proposed this change because the Cygwin sent 2 emails in 2 days,
whereas this worker is failing since it has been registered.

Victor
-- 
Night gathers, and now my watch begins. It shall not end until my death.

From greg at krypto.org  Wed Apr 10 20:23:12 2019
From: greg at krypto.org (Gregory P. Smith)
Date: Wed, 10 Apr 2019 17:23:12 -0700
Subject: [Python-buildbots] Disable notifiations on broken workers
In-Reply-To: <CA+3bQGGtN0jwKuoSD7_AL+2=M-6SvYMGnasv=2B2m6=P3zhBtw@mail.gmail.com>
References: <CA+3bQGGtN0jwKuoSD7_AL+2=M-6SvYMGnasv=2B2m6=P3zhBtw@mail.gmail.com>
Message-ID: <CAGE7PN+2GXssLHcnRHy91RLKt9vidczcBE2Y7V4tWn-gcy-amQ@mail.gmail.com>

On Wed, Apr 10, 2019 at 4:08 PM Victor Stinner <vstinner at redhat.com> wrote:

> Hi,
>
> I propose to disable email and IRC notifications on workers which were
> never green (tests always failed):
> https://github.com/python/buildmaster-config/pull/86
>
> * Alpine Linux
> * Cygwin
> * "AMD64 Clang UBSan 3." (3.6, 3.7 and 3.x, surprisingly, 2.7 is green)
>
> Does anyone have a good reason to keep notifications for these workers?
>

Agreed.  Lets not notify about intentionally unstable workers until we are
happy that they can only report regressions.  I can speak for the ubsan
bots - the output on stderr regardless of tests passing is of interest to
anyone looking at sanitizers (which is likely why 2.7 is green - there are
still things that could be looked into on stderr).  tests passing and
failing ideally wouldn't happen but it looks like there is one test tripped
up by the sanitizer (test_venv) for now.


>
> I proposed this change because the Cygwin sent 2 emails in 2 days,
> whereas this worker is failing since it has been registered.
>
> Victor
> --
> Night gathers, and now my watch begins. It shall not end until my death.
> _______________________________________________
> Python-Buildbots mailing list
> Python-Buildbots at python.org
> https://mail.python.org/mailman/listinfo/python-buildbots
>

From vstinner at redhat.com  Wed Apr 10 21:10:03 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Thu, 11 Apr 2019 03:10:03 +0200
Subject: [Python-buildbots] Disable notifiations on broken workers
In-Reply-To: <CAGE7PN+2GXssLHcnRHy91RLKt9vidczcBE2Y7V4tWn-gcy-amQ@mail.gmail.com>
References: <CA+3bQGGtN0jwKuoSD7_AL+2=M-6SvYMGnasv=2B2m6=P3zhBtw@mail.gmail.com>
 <CAGE7PN+2GXssLHcnRHy91RLKt9vidczcBE2Y7V4tWn-gcy-amQ@mail.gmail.com>
Message-ID: <CA+3bQGEuaYyMfjw5y15BmubP_b2LYAKtBvKAtj_s3+f53km=2Q@mail.gmail.com>

Ok, I deployed the new configuration.

Victor

Le jeu. 11 avr. 2019 ? 02:23, Gregory P. Smith <greg at krypto.org> a ?crit :
>
>
>
> On Wed, Apr 10, 2019 at 4:08 PM Victor Stinner <vstinner at redhat.com> wrote:
>>
>> Hi,
>>
>> I propose to disable email and IRC notifications on workers which were
>> never green (tests always failed):
>> https://github.com/python/buildmaster-config/pull/86
>>
>> * Alpine Linux
>> * Cygwin
>> * "AMD64 Clang UBSan 3." (3.6, 3.7 and 3.x, surprisingly, 2.7 is green)
>>
>> Does anyone have a good reason to keep notifications for these workers?
>
>
> Agreed.  Lets not notify about intentionally unstable workers until we are happy that they can only report regressions.  I can speak for the ubsan bots - the output on stderr regardless of tests passing is of interest to anyone looking at sanitizers (which is likely why 2.7 is green - there are still things that could be looked into on stderr).  tests passing and failing ideally wouldn't happen but it looks like there is one test tripped up by the sanitizer (test_venv) for now.
>
>>
>>
>> I proposed this change because the Cygwin sent 2 emails in 2 days,
>> whereas this worker is failing since it has been registered.
>>
>> Victor
>> --
>> Night gathers, and now my watch begins. It shall not end until my death.
>> _______________________________________________
>> Python-Buildbots mailing list
>> Python-Buildbots at python.org
>> https://mail.python.org/mailman/listinfo/python-buildbots



-- 
Night gathers, and now my watch begins. It shall not end until my death.

From db3l.net at gmail.com  Thu Apr 11 02:13:21 2019
From: db3l.net at gmail.com (David Bolen)
Date: Thu, 11 Apr 2019 02:13:21 -0400
Subject: [Python-buildbots] Windows 8.1 worker (bolen-worker8) retirement
Message-ID: <CAFirtYUKHEWS3FLuODjTDjE2cWFStaUA+hBWj8k=HqnGDN9qbA@mail.gmail.com>

My Windows 8.1 worker got hit on Wednesday by some "encrypt the world"
ransomware.  I'm not quite sure the path by which it reached the Azure VM,
but regardless, it's toast.

I don't think I see enough value in re-installation, given the existence of
the Windows 10 worker, plus I can probably bump some Windows 10 worker
resources with the budget freed up by Windows 8.  So I'm planning on
letting the Windows 8 worker end its run at this point.

-- David

From vstinner at redhat.com  Thu Apr 11 03:32:07 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Thu, 11 Apr 2019 09:32:07 +0200
Subject: [Python-buildbots] Windows 8.1 worker (bolen-worker8) retirement
In-Reply-To: <CAFirtYUKHEWS3FLuODjTDjE2cWFStaUA+hBWj8k=HqnGDN9qbA@mail.gmail.com>
References: <CAFirtYUKHEWS3FLuODjTDjE2cWFStaUA+hBWj8k=HqnGDN9qbA@mail.gmail.com>
Message-ID: <CA+3bQGENoJmrfVDFJ_egBzp4NwecVA6OzKRG1R8S1+PKXJPXRg@mail.gmail.com>

Thanks for providing this Windows 8.1 worker! Bye bye Windows 8.1 and
its annoying Start Menu!

Victor

Le jeu. 11 avr. 2019 ? 08:14, David Bolen <db3l.net at gmail.com> a ?crit :
>
> My Windows 8.1 worker got hit on Wednesday by some "encrypt the world"
> ransomware.  I'm not quite sure the path by which it reached the Azure VM,
> but regardless, it's toast.
>
> I don't think I see enough value in re-installation, given the existence of
> the Windows 10 worker, plus I can probably bump some Windows 10 worker
> resources with the budget freed up by Windows 8.  So I'm planning on
> letting the Windows 8 worker end its run at this point.
>
> -- David
> _______________________________________________
> Python-Buildbots mailing list
> Python-Buildbots at python.org
> https://mail.python.org/mailman/listinfo/python-buildbots



-- 
Night gathers, and now my watch begins. It shall not end until my death.

From vstinner at redhat.com  Thu Apr 11 07:02:59 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Thu, 11 Apr 2019 13:02:59 +0200
Subject: [Python-buildbots] Windows 3.x buildbots now also have a "load
 average"!
Message-ID: <CA+3bQGGfBXrokyZw5Q=waZxNxC-HPSnOkx7J+HQJ3DV1hmF2_w@mail.gmail.com>

Thanks for Ammar Askar:
https://github.com/python/cpython/pull/8357/files
https://bugs.python.org/issue34060

Example:

https://ci.appveyor.com/project/python/cpython/builds/23768195

...
0:04:40 load avg: 5.36 [321/420] test_xdrlib passed
0:04:41 load avg: 5.73 [322/420] test_future3 passed
0:04:41 load avg: 5.73 [323/420] test_unary passed
0:04:42 load avg: 5.73 [324/420] test_unpack_ex passed
0:04:49 load avg: 6.15 [325/420] test_tools passed
0:04:51 load avg: 6.15 [326/420] test_bz2 passed
0:04:52 load avg: 6.15 [327/420] test_robotparser passed
0:04:53 load avg: 7.58 [328/420] test_zlib passed
0:04:53 load avg: 7.58 [329/420] test_float passed
0:04:53 load avg: 7.58 [330/420] test_gdb skipped
...

Victor
-- 
Night gathers, and now my watch begins. It shall not end until my death.

From rodrigc at crodrigues.org  Fri Apr 12 01:37:37 2019
From: rodrigc at crodrigues.org (Craig Rodrigues)
Date: Thu, 11 Apr 2019 22:37:37 -0700
Subject: [Python-buildbots] Buildbot 2.1.0 and TLS between master and worker
Message-ID: <CAG=rPVd_wNtZuTkAC=-Kb_XUtqzqgx=aGLrx71Hxpyb1HJmdWw@mail.gmail.com>

Buildbot 2.1.0 (which is running at https://buildbot.python.org/all/ )
now supports TLS between a buildbot worker and the buildbot master.

There is an example of setting this up here:

http://docs.buildbot.net/current/manual/installation/worker.html#worker-tls-configuration

For folks interested in TLS between the buildbot master and buildbot worker,
that is something that the Python buildbot team might want to help get
going.
--
Craig

From vstinner at redhat.com  Fri Apr 12 08:21:20 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Fri, 12 Apr 2019 14:21:20 +0200
Subject: [Python-buildbots] Windows 8.1 worker (bolen-worker8) retirement
In-Reply-To: <CAFirtYUKHEWS3FLuODjTDjE2cWFStaUA+hBWj8k=HqnGDN9qbA@mail.gmail.com>
References: <CAFirtYUKHEWS3FLuODjTDjE2cWFStaUA+hBWj8k=HqnGDN9qbA@mail.gmail.com>
Message-ID: <CA+3bQGFQf0RUmr28vPEkUnaanXk1qxN2rtsTUDJ7L-mK+rxxNw@mail.gmail.com>

Right now, I still see worker in buildbot configuration. Can I remove
it? Or do you want to remove it?

https://github.com/python/buildmaster-config/blob/master/master/master.cfg

Victor

Le jeu. 11 avr. 2019 ? 08:14, David Bolen <db3l.net at gmail.com> a ?crit :
>
> My Windows 8.1 worker got hit on Wednesday by some "encrypt the world"
> ransomware.  I'm not quite sure the path by which it reached the Azure VM,
> but regardless, it's toast.
>
> I don't think I see enough value in re-installation, given the existence of
> the Windows 10 worker, plus I can probably bump some Windows 10 worker
> resources with the budget freed up by Windows 8.  So I'm planning on
> letting the Windows 8 worker end its run at this point.
>
> -- David
> _______________________________________________
> Python-Buildbots mailing list
> Python-Buildbots at python.org
> https://mail.python.org/mailman/listinfo/python-buildbots



-- 
Night gathers, and now my watch begins. It shall not end until my death.

From vstinner at redhat.com  Fri Apr 12 08:52:33 2019
From: vstinner at redhat.com (Victor Stinner)
Date: Fri, 12 Apr 2019 14:52:33 +0200
Subject: [Python-buildbots] Random failure when deploying the new buildbot
 config
Message-ID: <CA+3bQGFGsgka78YenNzO_YLOgrTHxWsm0UEfzfMdc5pzzrOcEw@mail.gmail.com>

Hi,

I just deployed the new config for
https://github.com/python/buildmaster-config/pull/88 but I got an
assertion error which gone away when I re-run "buildbot reconfig
master". Should I worry or not?

buildbot at virt-et2yi0:~$ /data/buildbot/venv/bin/buildbot checkconfig
master/master.cfg
Config file is good!
buildbot at virt-et2yi0:~$ /data/buildbot/venv/bin/buildbot reconfig master
sending SIGHUP to process 29619
2019-04-12 12:50:58+0000 [-] beginning configuration update
2019-04-12 12:50:58+0000 [-] Loading configuration from
'/data/buildbot/master/master.cfg'
2019-04-12 12:50:58+0000 [-] adding 1 new services, removing 1
2019-04-12 12:50:58+0000 [-] Starting factory
<buildbot.reporters.irc.IrcStatusFactory object at 0x2af30410d518>
2019-04-12 12:50:58+0000 [-] adding 10 new builders, removing 0
2019-04-12 12:50:58+0000 [IrcStatusBot,client] not scheduling
reconnection attempt
2019-04-12 12:50:58+0000 [-] Stopping factory
<buildbot.reporters.irc.IrcStatusFactory object at 0x2af2fb6fc358>
2019-04-12 12:51:04+0000 [-] initializing www plugin 'waterfall_view'
2019-04-12 12:51:04+0000 [-] initializing www plugin 'console_view'
2019-04-12 12:51:04+0000 [-] initializing www plugin 'grid_view'
2019-04-12 12:51:04+0000 [Broker,160838,8.43.85.216] during reconfig:
    Traceback (most recent call last):
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 654, in _runCallbacks
        current.result = callback(current.result, *args, **kw)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1475, in gotResult
        _inlineCallbacks(r, g, status)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1416, in _inlineCallbacks
        result = result.throwExceptionIntoGenerator(g)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/python/failure.py",
line 491, in throwExceptionIntoGenerator
        return g.throw(self.type, self.value, self.tb)
    --- <exception caught here> ---
      File "/data/buildbot/venv/lib/python3.6/site-packages/buildbot/master.py",
line 393, in doReconfig
        yield self.reconfigServiceWithBuildbotConfig(new_config)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1416, in _inlineCallbacks
        result = result.throwExceptionIntoGenerator(g)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/python/failure.py",
line 491, in throwExceptionIntoGenerator
        return g.throw(self.type, self.value, self.tb)
      File "/data/buildbot/venv/lib/python3.6/site-packages/buildbot/util/service.py",
line 49, in reconfigServiceWithBuildbotConfig
        yield svc.reconfigServiceWithBuildbotConfig(new_config)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1416, in _inlineCallbacks
        result = result.throwExceptionIntoGenerator(g)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/python/failure.py",
line 491, in throwExceptionIntoGenerator
        return g.throw(self.type, self.value, self.tb)
      File "/data/buildbot/venv/lib/python3.6/site-packages/buildbot/process/measured_service.py",
line 31, in reconfigServiceWithBuildbotConfig
        yield super(MeasuredBuildbotServiceManager,
self).reconfigServiceWithBuildbotConfig(new_config)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1416, in _inlineCallbacks
        result = result.throwExceptionIntoGenerator(g)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/python/failure.py",
line 491, in throwExceptionIntoGenerator
        return g.throw(self.type, self.value, self.tb)
      File "/data/buildbot/venv/lib/python3.6/site-packages/buildbot/util/service.py",
line 520, in reconfigServiceWithBuildbotConfig
        yield svc.reconfigServiceWithSibling(config_sibling)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1416, in _inlineCallbacks
        result = result.throwExceptionIntoGenerator(g)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/python/failure.py",
line 491, in throwExceptionIntoGenerator
        return g.throw(self.type, self.value, self.tb)
      File "/data/buildbot/venv/lib/python3.6/site-packages/buildbot/worker/base.py",
line 302, in reconfigServiceWithSibling
        yield self.updateWorker()
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1418, in _inlineCallbacks
        result = g.send(result)
      File "/data/buildbot/venv/lib/python3.6/site-packages/buildbot/worker/base.py",
line 509, in sendBuilderList
        d1 = self.attachBuilder(b)
      File "/data/buildbot/venv/lib/python3.6/site-packages/buildbot/worker/base.py",
line 514, in attachBuilder
        return builder.attached(self, self.worker_commands)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1613, in unwindGenerator
        return _cancellableInlineCallbacks(gen)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1529, in _cancellableInlineCallbacks
        _inlineCallbacks(None, g, status)
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 1421, in _inlineCallbacks
        status.deferred.callback(getattr(e, "value", None))
      File "/data/buildbot/venv/lib/python3.6/site-packages/twisted/internet/defer.py",
line 459, in callback
        assert not isinstance(result, Deferred)
    builtins.AssertionError:

2019-04-12 12:51:04+0000 [Broker,160838,8.43.85.216] WARNING: reconfig
partially applied; master may malfunction
Reconfiguration failed. Please inspect the master.cfg file for errors, correct
them, then try 'buildbot reconfig' again.
buildbot at virt-et2yi0:~$ /data/buildbot/venv/bin/buildbot reconfig master
sending SIGHUP to process 29619
2019-04-12 12:51:20+0000 [-] beginning configuration update
2019-04-12 12:51:20+0000 [-] Loading configuration from
'/data/buildbot/master/master.cfg'
2019-04-12 12:51:21+0000 [-] Starting factory
<buildbot.reporters.irc.IrcStatusFactory object at 0x2af3047c3c88>
2019-04-12 12:51:21+0000 [IrcStatusBot,client] not scheduling
reconnection attempt
2019-04-12 12:51:21+0000 [-] Stopping factory
<buildbot.reporters.irc.IrcStatusFactory object at 0x2af30410d518>
2019-04-12 12:51:25+0000 [-] initializing www plugin 'waterfall_view'
2019-04-12 12:51:25+0000 [-] initializing www plugin 'console_view'
2019-04-12 12:51:25+0000 [-] initializing www plugin 'grid_view'
2019-04-12 12:51:25+0000 [-] configuration update complete
Reconfiguration appears to have completed successfully

Victor
-- 
Night gathers, and now my watch begins. It shall not end until my death.

From zachary.ware+pydev at gmail.com  Fri Apr 12 10:01:31 2019
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Fri, 12 Apr 2019 09:01:31 -0500
Subject: [Python-buildbots] Random failure when deploying the new
 buildbot config
In-Reply-To: <CA+3bQGFGsgka78YenNzO_YLOgrTHxWsm0UEfzfMdc5pzzrOcEw@mail.gmail.com>
References: <CA+3bQGFGsgka78YenNzO_YLOgrTHxWsm0UEfzfMdc5pzzrOcEw@mail.gmail.com>
Message-ID: <CAKJDb-NLF_NTQsnAowrhCFL_Kfdw-R3Wc3UfjOpmfoHuqsMBkw@mail.gmail.com>

On Fri, Apr 12, 2019 at 7:52 AM Victor Stinner <vstinner at redhat.com> wrote:
> Hi,
>
> I just deployed the new config for
> https://github.com/python/buildmaster-config/pull/88 but I got an
> assertion error which gone away when I re-run "buildbot reconfig
> master". Should I worry or not?

I'm not too worried about it, but doing a restart (`./buildbot.sh
restart master`) might be a good idea anyway.  We're also due for
another update (2.2.0), which would require a restart anyway.

-- 
Zach

From cstratak at redhat.com  Thu Apr 18 10:02:19 2019
From: cstratak at redhat.com (Charalampos Stratakis)
Date: Thu, 18 Apr 2019 10:02:19 -0400 (EDT)
Subject: [Python-buildbots] Added a new ClangUnixInstalledBuild config
In-Reply-To: <51243658.18756261.1555595725020.JavaMail.zimbra@redhat.com>
Message-ID: <1256569835.18756978.1555596139598.JavaMail.zimbra@redhat.com>

Hello everyone,

I recently added a new ClangUnixInstalledBuild config for the buildbot fleet.

It inherits from UnixInstalledBuild and uses clang instead of gcc, and it currently runs on cstratak-fedora worker.

-- 
Regards,

Charalampos Stratakis
Software Engineer
Python Maintenance Team, Red Hat

From aixtools at felt.demon.nl  Thu Apr 25 06:47:48 2019
From: aixtools at felt.demon.nl (Michael Felt)
Date: Thu, 25 Apr 2019 12:47:48 +0200
Subject: [Python-buildbots] buildtimes, success-rate
Message-ID: <5CC19054.5020401@felt.demon.nl>

Hi.

Is there something missing from the AIX buildbots that there is no 
record for the buildtime? And, while I know my bot, runnig on xlc 
continues to fail the multiprocessing tests (as a bot) the gccfarm bot 
passes all tests, but has some link warnings (from a bad 3rd party library).

Besides having a "yellow" exit color (warnings) - is this also 
preventing the gccfarm AIX bot from showing as "successful" (in the graph)?

If there is something additional needed - please indicate what - if you 
know.

Thanks,
Michael

From zachary.ware+pydev at gmail.com  Thu Apr 25 09:51:57 2019
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Thu, 25 Apr 2019 08:51:57 -0500
Subject: [Python-buildbots] buildtimes, success-rate
In-Reply-To: <5CC19054.5020401@felt.demon.nl>
References: <5CC19054.5020401@felt.demon.nl>
Message-ID: <CAKJDb-NUk5F4WOBAYkZvChEOmbsH1bBa89gmb4x+x-Yow40OWA@mail.gmail.com>

On Thu, Apr 25, 2019 at 6:11 AM Michael Felt <aixtools at felt.demon.nl> wrote:
> Hi.
>
> Is there something missing from the AIX buildbots that there is no
> record for the buildtime?

I'm not sure what you mean.  Looking at
https://buildbot.python.org/all/#/builders/161 I see durations for
every build (and a sudden jump from 1 hour to 2 9 days ago).  Looking
at https://buildbot.python.org/all/#/builders/161/builds/1032 I see
durations for each step of the build.  All of that is tracked by the
master; nothing special required from the worker.

> And, while I know my bot, runnig on xlc
> continues to fail the multiprocessing tests (as a bot) the gccfarm bot
> passes all tests, but has some link warnings (from a bad 3rd party library).
>
> Besides having a "yellow" exit color (warnings) - is this also
> preventing the gccfarm AIX bot from showing as "successful" (in the graph)?

Yes; there must be no errors, no warnings, and no test failures (all
at the `test` step; compilation warnings in the `compile` step only
mark the `compile` step yellow) for a completely green build.  It is a
bit unfortunate that `make buildbottest` tries to rebuild modules that
have already failed to build; perhaps we could consider changing that.

-- 
Zach

From aixtools at felt.demon.nl  Sun Apr 28 09:29:22 2019
From: aixtools at felt.demon.nl (Michael)
Date: Sun, 28 Apr 2019 15:29:22 +0200
Subject: [Python-buildbots] buildtimes, success-rate
In-Reply-To: <CAKJDb-NUk5F4WOBAYkZvChEOmbsH1bBa89gmb4x+x-Yow40OWA@mail.gmail.com>
References: <5CC19054.5020401@felt.demon.nl>
 <CAKJDb-NUk5F4WOBAYkZvChEOmbsH1bBa89gmb4x+x-Yow40OWA@mail.gmail.com>
Message-ID: <6e679d77-1391-ab91-784f-8dca980b710b@felt.demon.nl>

On 25/04/2019 15:51, Zachary Ware wrote:
> On Thu, Apr 25, 2019 at 6:11 AM Michael Felt <aixtools at felt.demon.nl> wrote:
>> Hi.
>>
>> Is there something missing from the AIX buildbots that there is no
>> record for the buildtime?
> I'm not sure what you mean.  Looking at
> https://buildbot.python.org/all/#/builders/161 I see durations for
> every build (and a sudden jump from 1 hour to 2 9 days ago). 

About 9-10 days ago there were several changes parallel with a change to
setup.py (where -D XYZ was used, rather than -DXYZ).

The last revision with "normal time" for bot 161 is:
2b7f93b99afbe78e4e567d9252d9470d29f387c8 - with:

10 slowest tests:
- test_tools: 4 min 41 sec
- test_concurrent_futures: 4 min 16 sec
- test_tokenize: 3 min 59 sec
- test_subprocess: 3 min 35 sec
- test_lib2to3: 2 min 27 sec
- test_venv: 2 min 3 sec
- test_asyncio: 1 min 38 sec
- test_ssl: 1 min 28 sec
- test_io: 1 min 21 sec
- test_zipfile: 1 min 18 sec

the first with the jump to 2 hours is:
926b0cb5f688808dc11448a0bf3e452d1b92c232 - with:

10 slowest tests:
- test_tools: 13 min 56 sec
- test_tokenize: 10 min 53 sec
- test_lib2to3: 7 min 27 sec
- test_venv: 7 min 21 sec
- test_subprocess: 7 min 21 sec
- test_concurrent_futures: 7 min 9 sec
- test_zipfile: 3 min 38 sec
- test_io: 2 min 58 sec
- test_regrtest: 2 min 49 sec
- test_asyncio: 2 min 47 sec

No idea what is causing this - I have not made any updates, system
config changes, etc. to the bot to explain this.

So, what I was looking at (I'll try pasting a picture) are the three
tabs in the middle of the page "Build Requests", "Build times", "Success
Rate".


>  Looking
> at https://buildbot.python.org/all/#/builders/161/builds/1032 I see
> durations for each step of the build.  All of that is tracked by the
> master; nothing special required from the worker.
>
>> And, while I know my bot, runnig on xlc
>> continues to fail the multiprocessing tests (as a bot) the gccfarm bot
>> passes all tests, but has some link warnings (from a bad 3rd party library).
>>
>> Besides having a "yellow" exit color (warnings) - is this also
>> preventing the gccfarm AIX bot from showing as "successful" (in the graph)?
> Yes; there must be no errors, no warnings, and no test failures (all
> at the `test` step; compilation warnings in the `compile` step only
> mark the `compile` step yellow) for a completely green build. 

So, looking at bot https://buildbot.python.org/all/#/builders/10, as far
as the bot process is concerned - this is still a "failure".


>  It is a
> bit unfortunate that `make buildbottest` tries to rebuild modules that
> have already failed to build; perhaps we could consider changing that.
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-buildbots/attachments/20190428/3ae92bcd/attachment.sig>