public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: buildbot@sourceware.org, libc-alpha@sourceware.org
Subject: Re: glibc builder.sourceware.org integration
Date: Sat, 2 Jul 2022 21:45:49 +0200	[thread overview]
Message-ID: <YsCgbbGTTexYCU+B@wildebeest.org> (raw)
In-Reply-To: <Yr+awSjCvIIYBENG@elastic.org>

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


  reply	other threads:[~2022-07-02 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 22:23 Mark Wielaard
2022-07-01 12:00 ` Mark Wielaard
2022-07-01 22:24   ` Mark Wielaard
2022-07-02  1:09     ` Frank Ch. Eigler
2022-07-02 19:45       ` Mark Wielaard [this message]
2022-07-03 15:22         ` Dorian ROSSE
2022-07-03 16:37           ` Mark Wielaard
2022-07-04 15:17     ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YsCgbbGTTexYCU+B@wildebeest.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=fche@elastic.org \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).