From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, Benjamin Slade <beoram@gmail.com>
Subject: Re: Guix on aarch64
Date: Tue, 28 Aug 2018 15:22:04 -0400 [thread overview]
Message-ID: <87d0u2guub.fsf@netris.org> (raw)
In-Reply-To: <20180828190909.GA11946@jasmine.lan> (Leo Famulari's message of "Tue, 28 Aug 2018 15:09:09 -0400")
Leo Famulari <leo@famulari.name> writes:
> On Tue, Aug 28, 2018 at 09:57:49AM +0200, Ricardo Wurmus wrote:
>> I commented specifically on Leo’s statement about build debugging on
>> Cuirass:
>>
>> “I don't actually do any build debugging with Berlin yet because I
>> don't know how to use the interface effectively.”
>>
>> 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
next prev parent reply other threads:[~2018-08-28 19:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mutm72n7.fsf@jnanam.net>
[not found] ` <878t565k85.fsf@lassieur.org>
[not found] ` <87k1oq6wgf.fsf@jnanam.net>
2018-08-23 4:58 ` Guix on aarch64 Mark H Weaver
2018-08-23 16:09 ` Benjamin Slade
2018-08-24 10:32 ` Ludovic Courtès
2018-08-24 19:18 ` Ricardo Wurmus
2018-08-26 16:13 ` Mark H Weaver
2018-08-26 18:59 ` Leo Famulari
2018-08-27 8:04 ` Ricardo Wurmus
2018-08-27 18:54 ` Mark H Weaver
2018-08-27 19:11 ` Mark H Weaver
2018-08-27 19:26 ` Ricardo Wurmus
2018-08-27 21:05 ` Mark H Weaver
2018-08-27 21:56 ` Mark H Weaver
2018-08-28 5:39 ` Mark H Weaver
2018-08-28 7:57 ` Ricardo Wurmus
2018-08-28 10:00 ` Andreas Enge
2018-08-28 15:40 ` Mark H Weaver
2018-08-28 19:09 ` Leo Famulari
2018-08-28 19:22 ` Mark H Weaver [this message]
2018-08-27 19:50 ` Leo Famulari
2018-08-27 20:37 ` Ricardo Wurmus
2018-08-29 20:52 ` Joshua Branson
2018-08-30 20:47 ` Ricardo Wurmus
2018-08-30 9:49 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0u2guub.fsf@netris.org \
--to=mhw@netris.org \
--cc=beoram@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).