Hi Christophe, On Thu, Jul 07, 2022 at 03:50:51PM +0200, Christophe Lyon wrote: > As discussed on IRC we are going to enable workers on our Ampere "big" > machine. > > For a start, we are going to try with GDB, having 4 different docker > containers on the machine covering ubuntu-20.04/ubuntu-22.04 x > arm64/armhf, using 4 CPUs each. > > I am not sure if we need a single password for all workers, or 4 of them? You need 4 names, in theory the passwords could be the same for each, but I'll sent you 4 names with 4 different passwords (off-list). Lets name them arm64-ubuntu20_04, arm64-ubuntu22_04, armhf-ubuntu20_04 and armhf-ubuntu22_04. > For each of them that means: > ncpus:4 > maxcpus:4 > max_builds:1 OK. See the attached patch, 4 new workers each connected to a gdb CI builder. > Once these work, I'll add more containers for glibc, binutils and > hopefully GCC. Note that it might be helpful for keeping builds totally separate you can use a worker for multiple builders. Depending on the number of vcpus and memory available they can do the builds serially or in parallal (with max_builds > 1). > I think this small patch is desirable: > diff --git a/builder/containers/bb-start.sh b/builder/containers/bb-start.sh > index 31cdbc9..220e82e 100755 > --- a/builder/containers/bb-start.sh > +++ b/builder/containers/bb-start.sh > @@ -18,6 +18,7 @@ fi > > # Fill in the info visible in the buildbot website > # objcopy gives us the binutils version, iconv the glibc version > +mkdir -p $worker_dir/info > echo buildbot@sourceware.org > $worker_dir/info/admin > echo $IMAGE_NAME > $worker_dir/info/host > gcc --version | head -1 >> $worker_dir/info/host The info dir should have been created by buildbot-worker create-worker. BTW. The containers and the bb-start.sh script are somewhat over-complicated because they are written to be created and instantiated by the buildbot and so have severa layers of abstraction that aren't needed if you build the image and start the container upfront. Cheers, Mark