Re: glibc builder.sourceware.org integration

[Dorian ROSSE <dorianbrice@hotmail.fr>]

[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]

Hello,


How to build on Ubuntu?

I have ever tried without success the documentation doesn't bring the good help,

This is for build systemd version 251,

Each help will be good,

Now the server doesn't power up fully because it has error " userspace out of memory killer" thus I will bought ram,

I have this error because I have uninstall xcb, Wayland and libbluetooth3,

Thanks you in advance for your help,

Regards.


Dorian Rosse.
________________________________
From: Libc-alpha <libc-alpha-bounces+dorianbrice=hotmail.fr@sourceware.org> on behalf of Mark Wielaard <mark@klomp.org>
Sent: Saturday, July 2, 2022 9:45:49 PM
To: Frank Ch. Eigler <fche@elastic.org>
Cc: buildbot@sourceware.org <buildbot@sourceware.org>; libc-alpha@sourceware.org <libc-alpha@sourceware.org>
Subject: Re: glibc builder.sourceware.org integration

Hi Frank,

On Fri, Jul 01, 2022 at 09:09:21PM -0400, Frank Ch. Eigler via Libc-alpha wrote:
> > It is there now. I don't know why it wasn't there earlier.  Frank, is
> > there a delay between the bunsendb update and when the testruns show
> > up?
>
> Yes.  Sourceware runs a 15-minute timer to ingest data from
> bunsendb.git into the database.

Aha, ok, then it makes sense I didn't find it immediately.

BTW. For people who didn't see it yet, the builder frontpage
https://builder.sourceware.org/ contains little bunsen burner icons
next to the project or builder which are links to the recorded
testresults for that project or a particular builder so you can easily
dig into the results or compare results between bulds.

> (Yeah this could conceivably be done by yet another buildbot job,
> but I'm happier with a distinctly unprivileged process doing the
> work.)

Separation of processes/permissions is important. You can also do that
in the buildbot model, but it does take a bit more configuration than
just installing a cronjob. You could have a separate worker just for
the ingestion process. Then when the buildbot scheduler sees a change
in the bundendb.git it signals that worker to do a ingestion build
under its own process. Or you can use a Dependent or Triggerable
Scheduler to run a build against a different worker after a bunsen
upload step succeeds.

https://docs.buildbot.net/latest/manual/configuration/schedulers.html#dependent-scheduler
https://docs.buildbot.net/latest/manual/configuration/schedulers.html#sched-Triggerable

Cheers,

Mark


[-- Attachment #2: Type: text/html, Size: 5354 bytes --]