From zachary.ware+pydev at gmail.com  Mon Jul  2 09:25:31 2018
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Mon, 2 Jul 2018 08:25:31 -0500
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
Message-ID: <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>

On Mon, Jul 2, 2018 at 8:07 AM Tal Einat <taleinat at gmail.com> wrote:
>
> My home file-server is an Intel NUC with a Celeron CPU running Ubuntu
> 16.04. It compiles and runs Python just fine. It is always on (>99% uptime).
>
> Would you like me to set it up as another buildbot in our fleet?

I don't think we can have too many builders :).  However, we do
recommend that workers run on a separate VM or on an otherwise unused
machine for your security: if we find ourselves in the same situation
that Gentoo did this week, your builder will be running untrusted code
and causing who knows what kind of mayhem.  If you have mitigations in
place to your satisfaction, let me know and I'll send you credentials
to connect to the master.

Do you have any particular kind of build you'd like to run?  There are
a few combinations that we don't cover yet, like `--enable-shared` PGO
or installed (or both).

-- 
Zach

From vstinner at redhat.com  Mon Jul  2 09:52:48 2018
From: vstinner at redhat.com (Victor Stinner)
Date: Mon, 2 Jul 2018 15:52:48 +0200
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
Message-ID: <CA+3bQGHFY+4mE7+AG9b=ffFGHAoCzWQ5kc_2EL7XvfhLvpA5ZQ@mail.gmail.com>

2018-07-02 15:25 GMT+02:00 Zachary Ware <zachary.ware+pydev at gmail.com>:
> if we find ourselves in the same situation
> that Gentoo did this week, your builder will be running untrusted code
> and causing who knows what kind of mayhem.

Oh, I'm not aware of this issue. What happened?

> Do you have any particular kind of build you'd like to run?  There are
> a few combinations that we don't cover yet, like `--enable-shared` PGO
> or installed (or both).

Celeron sounds like "slow" to me. I don't think that PGO is a good
idea on such CPU.

Victor

From zachary.ware+pydev at gmail.com  Mon Jul  2 10:02:35 2018
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Mon, 2 Jul 2018 09:02:35 -0500
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CA+3bQGHFY+4mE7+AG9b=ffFGHAoCzWQ5kc_2EL7XvfhLvpA5ZQ@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
 <CA+3bQGHFY+4mE7+AG9b=ffFGHAoCzWQ5kc_2EL7XvfhLvpA5ZQ@mail.gmail.com>
Message-ID: <CAKJDb-OjGYBJQxgmBLJ-ya2Cb5uwUO2DD-eb6Zyj-p50ph3jTQ@mail.gmail.com>

On Mon, Jul 2, 2018 at 8:53 AM Victor Stinner <vstinner at redhat.com> wrote:
> 2018-07-02 15:25 GMT+02:00 Zachary Ware <zachary.ware+pydev at gmail.com>:
> > if we find ourselves in the same situation
> > that Gentoo did this week, your builder will be running untrusted code
> > and causing who knows what kind of mayhem.
>
> Oh, I'm not aware of this issue. What happened?

https://www.gentoo.org/news/2018/06/28/Github-gentoo-org-hacked.html

> > Do you have any particular kind of build you'd like to run?  There are
> > a few combinations that we don't cover yet, like `--enable-shared` PGO
> > or installed (or both).
>
> Celeron sounds like "slow" to me. I don't think that PGO is a good
> idea on such CPU.

That is true :).  Although it could be done as a daily build, like the
refleak build on my Gentoo bot.

-- 
Zach

From taleinat at gmail.com  Tue Jul  3 02:31:14 2018
From: taleinat at gmail.com (Tal Einat)
Date: Tue, 3 Jul 2018 09:31:14 +0300
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CAKJDb-OjGYBJQxgmBLJ-ya2Cb5uwUO2DD-eb6Zyj-p50ph3jTQ@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
 <CA+3bQGHFY+4mE7+AG9b=ffFGHAoCzWQ5kc_2EL7XvfhLvpA5ZQ@mail.gmail.com>
 <CAKJDb-OjGYBJQxgmBLJ-ya2Cb5uwUO2DD-eb6Zyj-p50ph3jTQ@mail.gmail.com>
Message-ID: <CALWZvp5SZGWzEWB4MbbqV09SzmEqenAA6n9bQ8z1VasJiOOM3A@mail.gmail.com>

On Mon, Jul 2, 2018 at 5:02 PM, Zachary Ware
<zachary.ware+pydev at gmail.com> wrote:

> On Mon, Jul 2, 2018 at 8:53 AM Victor Stinner <vstinner at redhat.com> wrote:
>
>> Celeron sounds like "slow" to me. I don't think that PGO is a good
>> idea on such CPU.
>
> That is true :).  Although it could be done as a daily build, like the
> refleak build on my Gentoo bot.

It's certainly not fast.

Please recommend which builds would be interesting to have this run.

Would it be possible to get some specific instructions how to set up
certain builds to run only once a day?

- Tal

From taleinat at gmail.com  Tue Jul  3 02:42:25 2018
From: taleinat at gmail.com (Tal Einat)
Date: Tue, 3 Jul 2018 09:42:25 +0300
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
Message-ID: <CALWZvp6YHpxPYTfXh=5q05RG7GDDkA5BaRY6hS+vWO1iOBcxXA@mail.gmail.com>

On Mon, Jul 2, 2018 at 4:25 PM, Zachary Ware
<zachary.ware+pydev at gmail.com> wrote:
> On Mon, Jul 2, 2018 at 8:07 AM Tal Einat <taleinat at gmail.com> wrote:
>>
>> My home file-server is an Intel NUC with a Celeron CPU running Ubuntu
>> 16.04. It compiles and runs Python just fine. It is always on (>99% uptime).
>>
>> Would you like me to set it up as another buildbot in our fleet?
>
> I don't think we can have too many builders :).  However, we do
> recommend that workers run on a separate VM or on an otherwise unused
> machine for your security [...]

Thanks for the advice!

Then I'll start setting up a VM on the machine. Afterwards I'll work
through the section on setting up a buildbot worker in the devguide.

- Tal

From vstinner at redhat.com  Tue Jul  3 02:49:09 2018
From: vstinner at redhat.com (Victor Stinner)
Date: Tue, 3 Jul 2018 08:49:09 +0200
Subject: [Python-buildbots] __Janitor buildbot
Message-ID: <CA+3bQGGmxbKyTphkjt+bkBJ=L5yyqNS83fziY4Hk-PTTe1n6MQ@mail.gmail.com>

Hi,

What is this builder "__Janitor"? It has no description and no branch,
no operating system filled.

Victor

From rodrigc at crodrigues.org  Tue Jul  3 03:06:23 2018
From: rodrigc at crodrigues.org (Craig Rodrigues)
Date: Tue, 3 Jul 2018 00:06:23 -0700
Subject: [Python-buildbots] __Janitor buildbot
In-Reply-To: <CA+3bQGGmxbKyTphkjt+bkBJ=L5yyqNS83fziY4Hk-PTTe1n6MQ@mail.gmail.com>
References: <CA+3bQGGmxbKyTphkjt+bkBJ=L5yyqNS83fziY4Hk-PTTe1n6MQ@mail.gmail.com>
Message-ID: <CAG=rPVdNRz5wrnowgwKd8dqCH87yOX3-4W6qt_mLRyqkz8fFhQ@mail.gmail.com>

__Janitor is an internal builder used by buildbot to clean things up:

http://docs.buildbot.net/latest/manual/installation/nine-upgrade.html#data-lifetime

There has been some talk about hiding it from the UI since it can be
confusing to
end-users of buildbot:

https://github.com/buildbot/buildbot/issues/3677

--
Craig

On Mon, Jul 2, 2018 at 11:53 PM Victor Stinner <vstinner at redhat.com> wrote:

> Hi,
>
> What is this builder "__Janitor"? It has no description and no branch,
> no operating system filled.
>
> Victor
> _______________________________________________
> Python-Buildbots mailing list
> Python-Buildbots at python.org
> https://mail.python.org/mailman/listinfo/python-buildbots
>

From vstinner at redhat.com  Tue Jul  3 04:43:50 2018
From: vstinner at redhat.com (Victor Stinner)
Date: Tue, 3 Jul 2018 10:43:50 +0200
Subject: [Python-buildbots] __Janitor buildbot
In-Reply-To: <CAG=rPVdNRz5wrnowgwKd8dqCH87yOX3-4W6qt_mLRyqkz8fFhQ@mail.gmail.com>
References: <CA+3bQGGmxbKyTphkjt+bkBJ=L5yyqNS83fziY4Hk-PTTe1n6MQ@mail.gmail.com>
 <CAG=rPVdNRz5wrnowgwKd8dqCH87yOX3-4W6qt_mLRyqkz8fFhQ@mail.gmail.com>
Message-ID: <CA+3bQGFf9rYnSzz_DDwwwR0NEK8aZAqF3GSScNk3XBuqoJ-NmA@mail.gmail.com>

At least, it would help to have a better description in the build and
in the worker.

Victor

2018-07-03 9:06 GMT+02:00 Craig Rodrigues <rodrigc at crodrigues.org>:
> __Janitor is an internal builder used by buildbot to clean things up:
>
> http://docs.buildbot.net/latest/manual/installation/nine-upgrade.html#data-lifetime
>
> There has been some talk about hiding it from the UI since it can be
> confusing to
> end-users of buildbot:
>
> https://github.com/buildbot/buildbot/issues/3677
>
> --
> Craig
>
> On Mon, Jul 2, 2018 at 11:53 PM Victor Stinner <vstinner at redhat.com> wrote:
>>
>> Hi,
>>
>> What is this builder "__Janitor"? It has no description and no branch,
>> no operating system filled.
>>
>> Victor
>> _______________________________________________
>> Python-Buildbots mailing list
>> Python-Buildbots at python.org
>> https://mail.python.org/mailman/listinfo/python-buildbots

From taleinat at gmail.com  Tue Jul  3 06:43:14 2018
From: taleinat at gmail.com (Tal Einat)
Date: Tue, 3 Jul 2018 13:43:14 +0300
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CALWZvp6YHpxPYTfXh=5q05RG7GDDkA5BaRY6hS+vWO1iOBcxXA@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
 <CALWZvp6YHpxPYTfXh=5q05RG7GDDkA5BaRY6hS+vWO1iOBcxXA@mail.gmail.com>
Message-ID: <CALWZvp40v5J+NTycN3zVqPS=mQzLp9R5pQffa+PHWsCAa7dg3Q@mail.gmail.com>

On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat at gmail.com> wrote:
> On Mon, Jul 2, 2018 at 4:25 PM, Zachary Ware
>> I don't think we can have too many builders :).  However, we do
>> recommend that workers run on a separate VM or on an otherwise unused
>> machine for your security [...]
>
> Thanks for the advice!
>
> Then I'll start setting up a VM on the machine. Afterwards I'll work
> through the section on setting up a buildbot worker in the devguide.

Alright, I've got Ubuntu 18.04 running in VirtualBox. I'm now at the
point where I need a name and password for the new buildbot worker.

- Tal

From taleinat at gmail.com  Tue Jul  3 11:38:05 2018
From: taleinat at gmail.com (Tal Einat)
Date: Tue, 3 Jul 2018 18:38:05 +0300
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CALWZvp40v5J+NTycN3zVqPS=mQzLp9R5pQffa+PHWsCAa7dg3Q@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
 <CALWZvp6YHpxPYTfXh=5q05RG7GDDkA5BaRY6hS+vWO1iOBcxXA@mail.gmail.com>
 <CALWZvp40v5J+NTycN3zVqPS=mQzLp9R5pQffa+PHWsCAa7dg3Q@mail.gmail.com>
Message-ID: <CALWZvp6_4u7eq3C0RX_XfKzJ4DM0NfjYV7wbpPES2pkmA3rp=Q@mail.gmail.com>

Alright, the worker looks to be up and running!

Thanks for the help Zachary!

On Tue, Jul 3, 2018 at 1:43 PM, Tal Einat <taleinat at gmail.com> wrote:

> On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat at gmail.com> wrote:
> > On Mon, Jul 2, 2018 at 4:25 PM, Zachary Ware
> >> I don't think we can have too many builders :).  However, we do
> >> recommend that workers run on a separate VM or on an otherwise unused
> >> machine for your security [...]
> >
> > Thanks for the advice!
> >
> > Then I'll start setting up a VM on the machine. Afterwards I'll work
> > through the section on setting up a buildbot worker in the devguide.
>
> Alright, I've got Ubuntu 18.04 running in VirtualBox. I'm now at the
> point where I need a name and password for the new buildbot worker.
>
> - Tal
>

From taleinat at gmail.com  Wed Jul 11 01:54:33 2018
From: taleinat at gmail.com (Tal Einat)
Date: Wed, 11 Jul 2018 08:54:33 +0300
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CALWZvp6_4u7eq3C0RX_XfKzJ4DM0NfjYV7wbpPES2pkmA3rp=Q@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
 <CALWZvp6YHpxPYTfXh=5q05RG7GDDkA5BaRY6hS+vWO1iOBcxXA@mail.gmail.com>
 <CALWZvp40v5J+NTycN3zVqPS=mQzLp9R5pQffa+PHWsCAa7dg3Q@mail.gmail.com>
 <CALWZvp6_4u7eq3C0RX_XfKzJ4DM0NfjYV7wbpPES2pkmA3rp=Q@mail.gmail.com>
Message-ID: <CALWZvp4CC50XYGW-UwhVLiKbXVdna_J0Uy2zJM7mgjwWRa1u5w@mail.gmail.com>

So, are we going to start sending builds to this worker?

On Tue, Jul 3, 2018 at 6:38 PM, Tal Einat <taleinat at gmail.com> wrote:

> Alright, the worker looks to be up and running!
>
> Thanks for the help Zachary!
>
> On Tue, Jul 3, 2018 at 1:43 PM, Tal Einat <taleinat at gmail.com> wrote:
>
>> On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat at gmail.com> wrote:
>> > On Mon, Jul 2, 2018 at 4:25 PM, Zachary Ware
>> >> I don't think we can have too many builders :).  However, we do
>> >> recommend that workers run on a separate VM or on an otherwise unused
>> >> machine for your security [...]
>> >
>> > Thanks for the advice!
>> >
>> > Then I'll start setting up a VM on the machine. Afterwards I'll work
>> > through the section on setting up a buildbot worker in the devguide.
>>
>> Alright, I've got Ubuntu 18.04 running in VirtualBox. I'm now at the
>> point where I need a name and password for the new buildbot worker.
>>
>> - Tal
>>
>
>

From zachary.ware+pydev at gmail.com  Wed Jul 11 10:50:27 2018
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Wed, 11 Jul 2018 09:50:27 -0500
Subject: [Python-buildbots] Any interest in an Intel Ubuntu buildbot?
In-Reply-To: <CALWZvp4CC50XYGW-UwhVLiKbXVdna_J0Uy2zJM7mgjwWRa1u5w@mail.gmail.com>
References: <CALWZvp4yPn0ws1wqAwMzDpC_jpZcayW01Vz62uUarsLaZtx9mA@mail.gmail.com>
 <CAKJDb-NSBYDbLBEL8z2GcNhVnXFr2=j5MCRdp2MaG4ogCemFzw@mail.gmail.com>
 <CALWZvp6YHpxPYTfXh=5q05RG7GDDkA5BaRY6hS+vWO1iOBcxXA@mail.gmail.com>
 <CALWZvp40v5J+NTycN3zVqPS=mQzLp9R5pQffa+PHWsCAa7dg3Q@mail.gmail.com>
 <CALWZvp6_4u7eq3C0RX_XfKzJ4DM0NfjYV7wbpPES2pkmA3rp=Q@mail.gmail.com>
 <CALWZvp4CC50XYGW-UwhVLiKbXVdna_J0Uy2zJM7mgjwWRa1u5w@mail.gmail.com>
Message-ID: <CAKJDb-OjLAxJheep24Nr81ya9oCpL4DYekTLL_XdUOtEVEkYAw@mail.gmail.com>

On Wed, Jul 11, 2018 at 12:54 AM Tal Einat <taleinat at gmail.com> wrote:
> So, are we going to start sending builds to this worker?

I did actually add builders to it yesterday, but just realized that
apparently nothing has been built in the past 4 days, likely due to
adding (and enforcing) HTTPS support to buildbot.python.org.  I've
tried to remove the redirect from HTTP to HTTPS which appears to have
restored service, and have asked Brett on Zulip to look at it from the
GitHub side.

> On Tue, Jul 3, 2018 at 6:38 PM, Tal Einat <taleinat at gmail.com> wrote:
>>
>> Alright, the worker looks to be up and running!
>>
>> Thanks for the help Zachary!
>>
>> On Tue, Jul 3, 2018 at 1:43 PM, Tal Einat <taleinat at gmail.com> wrote:
>>>
>>> On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat at gmail.com> wrote:
>>> > On Mon, Jul 2, 2018 at 4:25 PM, Zachary Ware
>>> >> I don't think we can have too many builders :).  However, we do
>>> >> recommend that workers run on a separate VM or on an otherwise unused
>>> >> machine for your security [...]
>>> >
>>> > Thanks for the advice!
>>> >
>>> > Then I'll start setting up a VM on the machine. Afterwards I'll work
>>> > through the section on setting up a buildbot worker in the devguide.
>>>
>>> Alright, I've got Ubuntu 18.04 running in VirtualBox. I'm now at the
>>> point where I need a name and password for the new buildbot worker.
>>>
>>> - Tal
>>
>>
>


-- 
Zach

From aixtools at felt.demon.nl  Sat Jul 21 07:41:42 2018
From: aixtools at felt.demon.nl (Michael Felt)
Date: Sat, 21 Jul 2018 13:41:42 +0200
Subject: [Python-buildbots] buildbot for AIX and xlc
Message-ID: <24eb0fc8-d23e-fe02-8fe1-21d2405d4ebd@felt.demon.nl>

Hi.

A couple of months back I built a test buildbot, to be sure I could. I 
am in the process of setting up a stable AIX VM and am willing to work 
on getting "buildbot" going.

ASAIK - the IBM provided buildbots are AIX 7.2 and gcc. I would be AIX 
7.1, (and maybe later also 6.1) but using vac (aka xlc) compiler. Again, 
not the latest - but clearly different from gcc.

As the wiki says to get an id before proceding with:

buildbot-worker create-worker buildarea buildbot.python.org:9020 workername workerpasswd

I would like a workername (ideally aixtools), etc..

Have a great weekend,

Michael aka aixtools

p.s. this is my personal system, in case that matters: a Power6


From aixtools at felt.demon.nl  Wed Jul 25 03:44:44 2018
From: aixtools at felt.demon.nl (Michael Felt)
Date: Wed, 25 Jul 2018 09:44:44 +0200
Subject: [Python-buildbots] Any interest for buildbot on AIX with xlc as
 compiler (rather than gcc)?
Message-ID: <35560159-7de3-1691-66fd-f37b72535f94@felt.demon.nl>

Now that I am on the mailing list - lets start again. (Note: the wiki 
only says send an email, not join a mailing list (first)).

I have a system, and a separate partition, setup with AIX 7.1 and 
Python3.7 et al.

Let me know you primary interests and I'll let you know how much I can 
support.

Regards,

Michael


From zachary.ware+pydev at gmail.com  Wed Jul 25 09:37:43 2018
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Wed, 25 Jul 2018 08:37:43 -0500
Subject: [Python-buildbots] Any interest for buildbot on AIX with xlc as
 compiler (rather than gcc)?
In-Reply-To: <35560159-7de3-1691-66fd-f37b72535f94@felt.demon.nl>
References: <35560159-7de3-1691-66fd-f37b72535f94@felt.demon.nl>
Message-ID: <CAKJDb-OnV0R0PfrYxokw1UgctVo1Vx2UGD6bqdn-CDLW1k71gg@mail.gmail.com>

Hi Michael,

On Wed, Jul 25, 2018 at 2:44 AM Michael Felt <aixtools at felt.demon.nl> wrote:
>
> Now that I am on the mailing list - lets start again. (Note: the wiki
> only says send an email, not join a mailing list (first)).

Sorry, your first mail did make it through, but I haven't had a chance
to properly respond yet.

> I have a system, and a separate partition, setup with AIX 7.1 and
> Python3.7 et al.

What type of processor is this system running?  We generally try to
name our workers `owner-os-processor`.  Once armed with that
information, I'll generate a worker name and password and send it to
you via private email.

Thanks for contributing a worker!
-- 
Zach