Hi Gavin,

Thanks. The buildbots report that they are attached now:

[[
2022-04-22 09:43:03+0200 [-] recording hostname in twistd.hostname
2022-04-22 09:43:03+0200 [-] Starting factory <buildbot_worker.pb.BotFactory 
object at 0x0000021A74600EB0>
2022-04-22 09:43:03+0200 [Broker,client] message from master: attached
2022-04-22 09:43:03+0200 [Broker,client] I have a leftover directory 
'svn-local' that is not being used by the buildmaster: you can delete it now
2022-04-22 09:43:03+0200 [Broker,client] I have a leftover directory 
'svn-test-run' that is not being used by the buildmaster: you can delete it now
2022-04-22 09:43:03+0200 [Broker,client] Connected to buildmaster; worker is 
ready
2022-04-22 09:43:03+0200 [Broker,client] sending application-level keepalives 
every 600 seconds
]]

Looks like the next step would be to re-enable the builds in the Subversion 
config. 

Nathan do you want to look at that? Or anybody else?
(I see that the Subversion config is renamed to .disabled and I assume quite a 
few builds don't apply any more)

Otherwise I will look into this, next weekend.

Thanks,
        Bert!

-----Original Message-----
From: Gavin McDonald <gmcdon...@apache.org> 
Sent: Thursday, April 21, 2022 10:18 PM
To: dev@subversion.apache.org
Subject: RE: Buildbot Migration

Hi Bert,

I emailed you some new connection details a few hours ago, let me know if your 
workers can connect and I'll see about enabling those jobs.

I have also changed the config for the ubuntu jobs to use asf hardware.

That leaves the mac builds - if nobody can source a mac I'll see what I can do 
my end

Gav...


On 2022/04/14 11:08:40 Bert Huijben wrote:
> I upgraded the win32 buildbots to python 3.10 and new buildbot and they now 
> try to connect to buildbot using the old credentials, but fail as the server 
> doesn't expect the bot to connect.
> 
> Can somebody try to obtain new credentials for or re-enable the old 
> credentials, so I can continue getting this SlikSvn sponsored bot back up.
> 
> 
> 
> Thanks,
>       Bert
> 
> -----Original Message-----
> From: Nathan Hartman <hartman.nat...@gmail.com>
> Sent: Sunday, April 10, 2022 5:33 PM
> To: Subversion Developers <dev@subversion.apache.org>
> Subject: Re: Buildbot Migration
> 
> On Tue, Jan 18, 2022 at 10:52 AM Nathan Hartman <hartman.nat...@gmail.com> 
> wrote:
> >
> > On Tue, Jan 18, 2022 at 10:45 AM Nathan Hartman 
> > <hartman.nat...@gmail.com> wrote:
> > >
> > > On Sun, Jan 16, 2022 at 3:56 PM Branko Čibej <br...@apache.org> wrote:
> > > >
> > > > On 16.01.2022 18:33, Nathan Hartman wrote:
> > > (snip)
> > > > > Are "svn-w2k3-local" and "svn-x64-macosx-dgvrs" currently the 
> > > > > only nonexistent nodes referenced by this script?
> > > >
> > > > Existent but not upgraded, at least in the case of the mac mini.
> > > >
> > > > Someday ...
> > >
> > > All the more reason to activate whatever is ready now and add 
> > > others back if/when they are ready. I'll go ahead and request to do 
> > > that...
> >
> > That's filed under INFRA-22761...
> 
> 
> As part of the recent migration from buildbot 0.8 to 3.2 and ci.a.o to 
> ci2.a.o, we have had no buildbots since late last year.
> 
> I think most of our buildbot configs should be able to run on 3.2, except for 
> svn-w2k3-local and svn-x64-macosx-dgvrs, so as a stopgap measure, I tried 
> commenting the aforementioned two and activating the config by renaming [3] 
> to remove the "-disabled" suffix.
> 
> However, Gavin McDonald comments on INFRA-22761: "I'm afraid we still can not 
> activate this config. There are no agents in which any of the builders can 
> use at this point."
> 
> Any ideas what we should do to get some buildbots back online?
> 
> [1] https://issues.apache.org/jira/browse/INFRA-22277
> 
> [2] https://issues.apache.org/jira/browse/INFRA-22761
> 
> [3] 
> https://svn.apache.org/repos/infra/infrastructure/buildbot2/projects/s
> ubversion.py
> 
> Cheers,
> Nathan
> 
> 

Reply via email to