From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Automatically building packages affected by submitted patches Date: Wed, 06 Mar 2019 16:09:20 +0100 Message-ID: <878sxsghun.fsf@gnu.org> References: <87tvgmfgkw.fsf@cbaines.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53608) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h1YAk-00019R-W4 for guix-devel@gnu.org; Wed, 06 Mar 2019 10:09:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h1YAj-0008FU-16 for guix-devel@gnu.org; Wed, 06 Mar 2019 10:09:30 -0500 Received: from hera.aquilenet.fr ([2a0c:e300::1]:42692) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h1YAh-00088K-29 for guix-devel@gnu.org; Wed, 06 Mar 2019 10:09:28 -0500 In-Reply-To: <87tvgmfgkw.fsf@cbaines.net> (Christopher Baines's message of "Fri, 01 Mar 2019 21:08:31 +0000") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Christopher Baines Cc: guix-devel@gnu.org Hello! Christopher Baines skribis: > For a specific example, here [5] is series 700 (a Patchwork id). There > are a number of intermediate steps, but this is the specification in > Cuirass [6]. > > 5: https://patchwork.cbaines.net/project/guix-patches/list/?series=3D700 > 6: https://cuirass.cbaines.net/jobset/series-700 Amazing! Looks like you=E2=80=99re really close to reaching your initial g= oal! > In terms of features I'd like to work towards next, the main thing on my > mind is doing something useful with the data from building these > packages. With the goal of displaying a check in Patchwork about the > build status of the affected packages, I need to compare what's been > build by my Cuirass instance, with what https://ci.guix.info/ has > built. To do this, my current plan is to have the Guix Data Service > monitor a number of Cuirass instances somehow, extract information from > them and store it. You'd then be able to get a comparison for the build > status using the results gathered from the two Cuirass instances from > the Guix Data Service. I=E2=80=99m also not sure why you need to compare things. Looking at and , it looks like Cuirass is already building the subset of packages that depend on the modified package(s): "subset":["r-dnacopy@1.56.0","r-dnacopy@1.56.0","coq-flocq@3.1.0","coq-in= terval@3.4.0"] (Though what is =E2=80=9Cr-dnacopy=E2=80=9D doing here?) So I would think that you only need to check the status of these 4 jobs, no? What would you need to ask ci.guix.info? Going forward, I agree with Ricardo that we could start running all this on ci.guix.info, whenever you think is the right time. I guess we could start with the Guix Data Service, which is already useful in itself. Thanks! Ludo=E2=80=99.