From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 646493858C2F; Sat, 2 Jul 2022 19:45:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 646493858C2F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x0e.wildebeest.org [172.31.17.144]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 83B22302AB2C; Sat, 2 Jul 2022 21:45:50 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 121A72E81623; Sat, 2 Jul 2022 21:45:50 +0200 (CEST) Date: Sat, 2 Jul 2022 21:45:49 +0200 From: Mark Wielaard To: "Frank Ch. Eigler" Cc: buildbot@sourceware.org, libc-alpha@sourceware.org Subject: Re: glibc builder.sourceware.org integration Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: buildbot@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "The https://builder.sourceware.org/ buildbot" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2022 19:45:56 -0000 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