From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: Guix on aarch64 Date: Tue, 28 Aug 2018 15:22:04 -0400 Message-ID: <87d0u2guub.fsf@netris.org> References: <87k1oq6wgf.fsf@jnanam.net> <87bm9tbrx9.fsf@netris.org> <87zhxcoy0p.fsf@gnu.org> <87efelw1fr.fsf@netris.org> <20180826185922.GB18912@jasmine.lan> <87tvng1bib.fsf@elephly.net> <87bm9ntyjh.fsf@netris.org> <87zhx7bohb.fsf@elephly.net> <87o9dnsep0.fsf@netris.org> <87r2iic48y.fsf@elephly.net> <20180828190909.GA11946@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36457) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fujaY-0002Dt-F0 for guix-devel@gnu.org; Tue, 28 Aug 2018 15:23:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fujaV-0006jx-4T for guix-devel@gnu.org; Tue, 28 Aug 2018 15:23:42 -0400 In-Reply-To: <20180828190909.GA11946@jasmine.lan> (Leo Famulari's message of "Tue, 28 Aug 2018 15:09:09 -0400") 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: Leo Famulari Cc: guix-devel@gnu.org, Benjamin Slade Leo Famulari writes: > On Tue, Aug 28, 2018 at 09:57:49AM +0200, Ricardo Wurmus wrote: >> I commented specifically on Leo=E2=80=99s statement about build debuggin= g on >> Cuirass: >>=20 >> =E2=80=9CI don't actually do any build debugging with Berlin yet bec= ause I >> don't know how to use the interface effectively.=E2=80=9D >>=20 >> This did not sound like a severe problem with Cuirass to me, but rather >> a problem that could be fixed by adding minor features to Cuirass like >> the display of build logs. Leo, could you please tell us what missing >> feature in the Cuirass web interface is the most urgent for you to use >> the interface effectively? > > My apologies in advance if these features already exist in the Cuirass > web interface! I didn't find them yet. > > I mostly use Hydra for two things: > > 1) I use it to manage large branch re-builds (e.g. core-updates) by > looking at the lists of failed builds for the lastest evaluation of that > particular "jobset" (i.e. Git branch). > > Hydra gives a list of tabs like this that are helpful: > > Aborted jobs (2) > Newly failing jobs (2) > Newly succeeding jobs (1) > New jobs (29) > Removed jobs (23) > Still failing jobs (2425) > Still succeeding jobs (20470) > Queued jobs (675) > Inputs > > I might also compare the evaluation to another evaluation of the same > jobset, or against another jobset (usually master). > > The concept of "dependency failures" and their reporting is also really > helpful (i.e "foo was not built because its dependency bar failed"). Right, these are all indispensible tools. > Also, I use the Hydra web interface to start jobset evaluations and > restart particular package builds, and to restart all builds that were > skipped due to dependency failures. These are too, although "restart all dependency failures", which I hastily added, is too crude of a tool in my opinion. I've since cooked up a PostgreSQL transaction which does something better: restart all dependency failures that were caused by a particular failed derivation. That should be what we aim for in Cuirass, I think. > 2) Checking build logs of a particular package to see if a failure or > success is reproducible on the build farm. Yes, this too. Mark