unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Continuous integration - automatic EMAIL
Date: Mon, 12 Oct 2020 21:12:54 +0200	[thread overview]
Message-ID: <CAJ3okZ2K0KxW60XnREJZNvedL_a53cNG87rW+3aoqBg6+vGxBg@mail.gmail.com> (raw)
In-Reply-To: <87362jsl6s.fsf@gnu.org>

Hi,

On Mon, 12 Oct 2020 at 14:06, Ludovic Courtès <ludo@gnu.org> wrote:

> >> Please, can we have the build servers send build failures to guix-devel
> >> instead of hoping that people check manually?  I have other things to do
> >> in my life than to poll random servers every few hours.
> >
> > That feature is definitely on my list. Fixing Cuirass and improving the
> > build throughput is already a hard task, but I'm getting there. In the
> > meantime, if people want to join Cuirass debugging party, they are more
> > than welcome!

[...]

> Caveat: my experience with Hydra is that you immediately receive too
> much mail.  Initially Hydra would send one message per failed build,
> which was then changed to one message at each status change (from
> “success” to “failure” and vice versa), but that was still too much.  I
> think eventually it was change to email only the committers of the
> offending commits, which is probably the best option.

If "guix weather -m" is improved, does it fill the gap?  Because it is
exactly doing what is required, isn't?  But it is not suitable for
this purpose because of UI.  I mean:

--8<---------------cut here---------------start------------->8---
$ cat /tmp/spec.scm
(specifications->manifest (list "emacs" "gcc-toolchain" "python-umap-learn"))

$ guix weather -m /tmp/spec.scm
computing 49 package derivations for x86_64-linux...
looking for 66 store items on https://ci.guix.gnu.org...
https://ci.guix.gnu.org
  97.0% substitutes available (64 out of 66)
  at least 340.7 MiB of nars (compressed)
  534.1 MiB on disk (uncompressed)
  0.001 seconds per request (0.0 seconds in total)
  1,768.0 requests per second
  'https://ci.guix.gnu.org/api/queue?nr=1000' returned 504 ("Gateway Time-out")
--8<---------------cut here---------------end--------------->8---

The information is here but I do not know which ones are fine and
which ones are failing.  If an option like "--raw" (or "--plain" or
"--exhaustive" or "--name-it" :-)) could display the status of all the
66 packages, then I think it would ease the detection of the
regresion.  For example,

  OK: emacs
  FAIL: python-umap-learn
  [...]

then it is doable to have a shell script parsing this output and I can
feed "git bisect".  Somehow.

WDYT?

All the best,
simon


  reply	other threads:[~2020-10-12 19:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 15:39 Continuous integration - automatic EMAIL Danny Milosavljevic
2020-10-07 15:52 ` Mathieu Othacehe
2020-10-12 12:06   ` Ludovic Courtès
2020-10-12 19:12     ` zimoun [this message]
2020-10-13 13:59       ` Ludovic Courtès
2020-10-07 22:20 ` raingloom

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=CAJ3okZ2K0KxW60XnREJZNvedL_a53cNG87rW+3aoqBg6+vGxBg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=othacehe@gnu.org \
    /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).