From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Hackathon: Mumi and Cuirass Date: Sat, 04 May 2019 08:19:29 +0100 Message-ID: <878svmk7pa.fsf@cbaines.net> References: <875zqrgqlf.fsf@elephly.net> 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]:58743) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMoxM-0006D0-FP for guix-devel@gnu.org; Sat, 04 May 2019 03:19:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMoxK-0000ko-Kn for guix-devel@gnu.org; Sat, 04 May 2019 03:19:36 -0400 Received: from mira.cbaines.net ([212.71.252.8]:51926) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMoxK-0000kX-6S for guix-devel@gnu.org; Sat, 04 May 2019 03:19:34 -0400 Received: from localhost (cpc102582-walt20-2-0-cust14.13-2.cable.virginm.net [86.27.34.15]) by mira.cbaines.net (Postfix) with ESMTPSA id DCCD316F08 for ; Sat, 4 May 2019 08:19:31 +0100 (BST) Received: from capella (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id 1e3f8c14 for ; Sat, 4 May 2019 07:19:31 +0000 (UTC) In-reply-to: <875zqrgqlf.fsf@elephly.net> 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: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ricardo Wurmus writes: > Hey there, > > now that Guix 1.0 is out I think it=E2=80=99s a good time to improve our = tools > to allow us to better identify problems with package builds and to > better respond to bug reports and patch submissions. ... > 2) Cuirass > > Cuirass has a web interface: https://ci.guix.gnu.org/ > > Unfortunately, it doesn=E2=80=99t yet enable us to answer questions like: > > - What packages are currently failing to build on aarch64? > - What is the history of icecat builds on i686? > - Can you show me all builds matching =E2=80=9Crust=E2=80=9D across all a= rchitectures? > - What builds are blocked because of this one failing build? > > Implementing features that would allow us to better see the build status > for all of our supported architectures would be very welcome. It would > be even better if we could also see an overview of our build nodes and > what they are currently doing =E2=80=93 how many build slots are still > available? Why is only one of the nodes doing any work? > > We have the freedom to integrate Cuirass more closely with the rest of > Guix and the offloading framework, so this seems like a good target. > > If you find this kind of project interesting please get in touch! You > don=E2=80=99t need to know how to do any of these tasks as long as you are > motivated to discuss this and help us find solutions together. > > Let=E2=80=99s do this! I mentioned some things which seem related to this in this email [1], but one of the enhancements I'm specifically interested in getting in to Cuirass is a way to provide subscriptions to the build information. This would enable "listening" to Cuirass, to get a near real time stream of events, build information, things like that. I previously tried scraping build information in to the Guix Data Service, and you can see some data here [2], but that was slow, and I was potentially missing builds. I think some kind of publish/subscribe model would work out much better. 1: https://lists.gnu.org/archive/html/guix-devel/2019-04/msg00094.html 2: https://prototype-guix-data-service.cbaines.net/builds > - What packages are currently failing to build on aarch64? > - What is the history of icecat builds on i686? > - Can you show me all builds matching =E2=80=9Crust=E2=80=9D across all a= rchitectures? > - What builds are blocked because of this one failing build? On the subject of questions like these, I would hope that if the Guix Data Service had up to date build information, it wouldn't be too difficult to add the necessary pages to make answering these questions easy. At the moment, as I say, there's no up to date information on builds, and the only page I've added a form for comparing derivations between two revisions ([3] for example). 3: https://prototype-guix-data-service.cbaines.net/compare/derivations?base= _commit=3D094aaa1a1e81b6c5461c1a2aa8ccd9019faa97ec&target_commit=3D4ee55938= de315ac965c12a99f5dc98f48ac2cc83 Now I'm not saying that I think it would be bad if Cuirass had a more detailed web interface, but even if it did, I'd still be interested in gathering up all the build information, as one thing I'm excited about for the future is the possibility of having multiple independent build farms. In my mind, reproducible builds + multiple independant build farms is the path towards trusted substitutes. From a users perspective, I'm imaginging setting some policy where I trust substitutes if berlin, and some other build farm agree on the output. But for a overall view of what's going on, this is where I see the value of gathering up build information from potentially many build farms in to one place. Now that I've got some updated patches for Patchwork up [4], I'll hopefully be able to make some time to work on this area over the coming weeks. 4: https://issues.guix.info/issue/33185#38 Thanks, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAlzNPQFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XeEYQ//UcLFX7d1dPBT4sjg0IWTpkyLNmo8I0ltnylCFxY5RVFuIcgNMnK+qfKx Vl5guvaYmydFOqpS/tmrKw7FtyG+sSVD3LtrdP4AdPh0Dc6kLQK/3/YOIU6ZD386 IefGkdP9qLFI3go91zHp0ogR+Cvp8NhsHLvTa/t1wKjP0NQyjbUAgeTaorvPAxxH 4QBRhwMdGrw209M8xMYyarv9iP0J6NfJKejFBTBw49hq78bRFFUcxvzpoJA9XYIf kerfvfd5mSbx5YUMriYsPI1TxsCj6T3gjeQ1iPs++Ic48A+ORjYR8M1YOVOAtciT aCkpUFI7lmioBVcBD3ie/ec25ASdUaORD9J9OFTKpcSleiy10R4+MoweFiY57rhd IXHZnYeD/k5vg2DHo7YFIRm/NEYGiRDVTSbKRC+zqONPEXukaZRYQToUMin0AJbg YrK85o2t/tmaywo8x0kaBMIBUdF5hOm477g0sx+Hy+SsJO7ETaaIuhrR1+bcYzB4 65/Ln2nBD4dZIiYN4e24qL0mjjdb4NYz97nK7plpX6rnq/fBKkzZqdyxRlG/9KXb oAp146WxZvCyYcfE9m/qnNrUB0eHDs3jIXIZwafcNHdZCCBGAHlHd17ImY2kxgvF A2NWkfrLmthRRNQ9hRcltR+d+U0NyoUn9hkDrwlpPUyrE/ReXhc= =ARJ9 -----END PGP SIGNATURE----- --=-=-=--