From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Automatically building packages affected by submitted patches Date: Wed, 06 Mar 2019 19:39:48 +0000 Message-ID: <875zsvg5bv.fsf@cbaines.net> References: <87tvgmfgkw.fsf@cbaines.net> <878sxsghun.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51842) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h1cOQ-0001wk-NU for guix-devel@gnu.org; Wed, 06 Mar 2019 14:39:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h1cOP-0002RX-6w for guix-devel@gnu.org; Wed, 06 Mar 2019 14:39:54 -0500 In-reply-to: <878sxsghun.fsf@gnu.org> 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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > 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= goal! Thanks :) >> 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-= interval@3.4.0"] > > (Though what is =E2=80=9Cr-dnacopy=E2=80=9D doing here?) The query in the Guix data service to determine what's changed between two revisions can't handle with two packages having the same name. It's been fixed now, but there were two definitions of the r-dnacopy package. > 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? Yeah, knowing what the after effect of the patches are is pretty useful, but I think that being able to compare the before and after state would give an even more complete picture. Consider if a patch affects 10 packages, and with that patch, 6 of the ten affected packages fail to build. If previously all 10 of those packages build successfully, then maybe this patch is a bit of a step backwards. However, if previously all 10 of these packages failed to build, then this patch is a definite improvement. So, I think it would be useful to gather the information from ci.guix.info about what packages have built and failed to build so that this can be used to reveal more about the effect of patches. > 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. Great, I'm not sure it's quite ready yet, but I think setting up the Guix Data Service as more of a proper thing would be a good step forward. Thanks, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAlyAIgRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XfMOQ//TrtOAXhrdSb1lStgroftH8I3C9zhu4choDcvGjggv97YHA3YiboiZ0Q2 dKtoFWaw6SgRwKkvMgGSgaQ/vIDp+V+ACiC2/iyFHWBOBloAMd6vrFd2Jk+6uD0n XkKb7BiNh8/Rg8A6PRxxweNNKpApA2pbZZ/rLwOstWoUqVs9UWUBcWq5Uuj9j7Uo dtVnPgJ3jdJd0m0VcExEb5WU3F8zaCfGVA5D/3LCR2eJjB4/o+vc6PmBr/ejlYJT XqWMzQXqk/9Kjbr4KxCclqGYdZ9qYCshrsyoEQw1Ik6vyj5AnBkCm6kAymapNY3x usqk1mxH7kx1RHhBssftShvgqJ/y5n/rZYsIsfQ0jA0tE5qGaLv9UwzQZwcgRbpo EI1oeU5s5kdJTPgGy5Aju6SvXnjdwzfrg9FJim64nSdO0tXgs2lOeZ+cgHbE2HBD 03uDz6VOlzs512Kee76j0A/aeMRlp4t5cC+1Bc5E/F6GlgAMdR2sbV3zz5qbya/c /vs5o4r75JwA2xL2ekrG8IJJA8yYqYZqtLV7dzox2ahB9CHQAXfenBGrFulmn84B OP+Hoh13HispaH9adh+iUereI1C1PBGZBlcVwV4wUBwR/aE+5nYjoIJVTlqYWFwv 88Ids25xTIEi83AExgFQBrP94jgBmek0Y2OitaaJczLsLpaML38= =r5Fn -----END PGP SIGNATURE----- --=-=-=--