[flang-dev] Flang Buildbot

[Brian Friesen via flang-dev]

Hi Carol + Michael,

On Wed, Apr 22, 2020 at 12:52 PM Michael Kruse <llvm at meinersbur.de> wrote:
> To confirm the buildslave works, connect it to port 9994. The results
> are reported to lab.llvm.org:8014
>
> Once we see that the builder works and is not flaky (randomly fails
> e.g. because of timeouts), switch the buildslave to connect to port
> 9990. Results will be reported at lab.llvm.org:8011 and lab.llvm.org
> will send out blame mails.
>
> It is important to use buildbot version 0.8.5 EXACTLY. Other versions
> do connect successfully (i.e. no check for version mismatch), but fail
> at some other stage. For me it was that "git" on the slave was not
> found.
>
>
> > - Step 9 of that page says "Send a patch which adds your build slave
> > and your builder to zorg." What does that mean? I searched a bit and
> > found this GitHub repository: https://github.com/llvm/llvm-zorg. Does
> > step 9 consist of sending a GitHub pull request to that repository
> > with the buildbot info?
>
> Upload a patch like the following:
>
> https://reviews.llvm.org/D75127
>
> >  - Assuming that the above mentioned GitHub page is the correct page
> > for 'zorg', what is the meaning of the properties 'jobs' and
> > 'max_builds'? e.g., this buildbot
> > (https://github.com/llvm/llvm-zorg/blob/master/buildbot/osuosl/master/config/slaves.py#L14)
> > has `jobs=24` and `max_builds=2`.
>
> 'jobs' typically is the '-j' parameter for ninja. It depends on the
> builder, of which you will define your own (in builders.py).
>
> 'max_builds' is the number of buildbot builds the buildslave is
> allowed to do concurrently (I think). I don't recommend that, there
> should be enough parallelism in the compilation.

Thank you for the clarifications. This is helpful. NERSC systems are
down for maintenance today so I will continue this effort when they
come back.