[llvm-dev] Help needed setting up a new buildbot for linux-sparcv9 and other targets

[John Paul Adrian Glaubitz via llvm-dev]

Hi Galina!

On 10/22/20 7:41 AM, Galina Kistanova wrote:
> Any distinct unused yet name which represents the build worker you are
> about to introduce is fine. For example, "linux-sparcv9", "linux-ppc32",
> "linux-mips", and "linux-m68k" look good. You could specify builddir to be
> the same as the worker name. This would keep things simple.

Is there any naming scheme that the other buildbot-workers are using or are the
names just random?

And why does the buildddir have to be unique? Isn't that local on the buildbot-
worker?

> I can assign passwords to your workers or you can choose whatever password
> you want and send directly to me. Please let me know if you need my public
> pgp key for secure communication.

Yes, your GPG key would be appreciated although I guess I can find it on the
public servers assigned to your email?

> We do not accept changes to zorg at this time because of the upgrade to a
> newer version of buildbot. The repository is locked and I'm in the middle
> of preparing a set of patches you will need to base your changes on. I hope
> this will be done early next week.

OK, noted.

> Anyway, once the llvm-zorg has all the changes for the new buildbot, you
> will need to propose a patch. Please note that the below explanation is
> based on the new file names which are not available yet in the github.
> 
> To add your workers to LLVM buildbot, you will need to propose a patch for
> buildbot/osuosl/master/config/workers.py which adds the workers, and for
> buildbot/osuosl/master/config/builders.py to add your build configurations
> which use your workers. If you are up to building self hosting clang and
> llvm, then please use UnifiedTreeBuilder.

OK.

> If you will elaborate what build configuration you are after for your bots,
> I might give you a good example to follow or will help you with the patch.

Selfhosting LLVM and clang would be my goal on 64-bit SPARC on Linux.

The machine has 64 vCPUs and 32 GiB of RAM. Running Debian unstable with
the latest versions of GCC, CMake and Binutils. Ninja is available, too.

> I assume you already made sure you can build locally on each of those
> workers what you are after.
Yep. That works fine. Although there is currently one regression on SPARC
which I already reported to the list.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz at debian.org
`. `'   Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913