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?
- Tal Einat
On Mon, Jul 2, 2018 at 8:07 AM Tal Einat <taleinat@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
2018-07-02 15:25 GMT+02:00 Zachary Ware <zachary.ware+pydev@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-sharedPGO or installed (or both).
Celeron sounds like "slow" to me. I don't think that PGO is a good idea on such CPU.
Victor
On Mon, Jul 2, 2018 at 8:53 AM Victor Stinner <vstinner@redhat.com> wrote:
2018-07-02 15:25 GMT+02:00 Zachary Ware <zachary.ware+pydev@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-sharedPGO 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
On Mon, Jul 2, 2018 at 5:02 PM, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
On Mon, Jul 2, 2018 at 8:53 AM Victor Stinner <vstinner@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
On Mon, Jul 2, 2018 at 4:25 PM, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
On Mon, Jul 2, 2018 at 8:07 AM Tal Einat <taleinat@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
On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat@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
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@gmail.com> wrote:
On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat@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
So, are we going to start sending builds to this worker?
On Tue, Jul 3, 2018 at 6:38 PM, Tal Einat <taleinat@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@gmail.com> wrote:
On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat@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
On Wed, Jul 11, 2018 at 12:54 AM Tal Einat <taleinat@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@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@gmail.com> wrote:
On Tue, Jul 3, 2018 at 9:42 AM, Tal Einat <taleinat@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
participants (3)
-
Tal Einat -
Victor Stinner -
Zachary Ware