glibc builder.sourceware.org integration

[Mark Wielaard]

Hi,

We have a shared buildbot for all Sourceware and GNU Toolchain
projects: https://builder.sourceware.org/
There are a couple of glibc builders now:
https://builder.sourceware.org/buildbot/#/builders?tags=glibc

The compile-only builders, glibc-debian-i386, glibc-debian-ppc64,
glibc-fedora-ppc64le, glibc-fedora-s390x, glibc-opensuseleap-x86_64
and glibc-opensusetw-x86_64 are all green. The builds are pretty quick
(using ccache) and take a couple of minutes at most. So they run on
each separate commit to the master branch.

It currently doesn't include arm64 and armhf builds, but those could
be added (the current boards are somewhat slow, but we will hopefully
get some faster hardware soon).

email notification of build failures hasn't been setup up yet. When we
set it up should it also notify the libc-alpha mailing list when a
build failure is detected? Only the first build failure will sent an
email till the build is restored.

There are currently two builders which do a make && make check.
glibc-fedora-x86_64 and glibc-fedrawhide-x86_64. The first is a
container build of fedora-latest (f36). The second is a fedora rawhide
VM.

The container builder has a couple of failures for which I just sent
patches. With those patches the build should turn green. At which
point we can also use it to detect test regressions.

Doing a full make && make check in the container takes ~15 to ~20
minutes and so isn't don't on every individual build, but batches up
changes till there have been none for 10 minutes. So it won't run
behind. It should detect a commit that caused a regression within 30
minutes. All test results (including all .out files) are uploaded into
the bunsendb for analysis:
https://builder.sourceware.org/testruns/?has_keyvalue_like_k=testrun.git_describe&has_keyvalue_like_v=%25glibc%25

Not all hardware is powerful enough to do a full make check on every
commit. But it would be good to make them do some real tests and not
just do a compile-only run. Is there a good, small, quick, sub-test
that could be added?

gdb and binutils are experimenting with git user try branches so they
can do pre-commit checking:
https://sourceware.org/pipermail/binutils/2022-June/121293.html
We can setup the same for glibc. Which we then can use for patchwork
integration.

Next week we should get more hardware and we can setup more full
builders for different configurations. Please contact
buildbot@sourceware.org with ideas and/or to help out with the setup
(which is in a public git repo, see the builder project homepage).

Cheers,

Mark