all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
	"Clément Lassieur" <clement@lassieur.org>,
	"Tatiana Sholokhova" <tanja201396@gmail.com>
Subject: Re: Web interface pushed
Date: Thu, 2 Aug 2018 21:21:36 +0200	[thread overview]
Message-ID: <CAL7_Mo-EM2UkmScMrXP6cGwxjYtZP3BtgVas274zgagWrACgNw@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=pjirjcep_S0J0Wu3sNA82T51xQ=YtrZf3wvt_AzAZYy_Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

Le jeu. 2 août 2018 à 20:49, Gábor Boskovits <boskovits@gmail.com> a écrit :

> Clément Lassieur <clement@lassieur.org> ezt írta (időpont: 2018. aug. 2.,
> Cs, 18:49):
>
>> Hi Gábor,
>>
>> Gábor Boskovits <boskovits@gmail.com> writes:
>>
>> > Also most of the time the results differing from the results in the
>> > previous evaluations are the most interesting.
>> > Can we get this kind of information somehow?
>>
>> About that, I am preparing a commit that would get Cuirass to stop
>> building all derivations, but only the ones that don't exist yet.
>> That's https://bugs.gnu.org/32190.  For example, Cuirass wouldn't build
>> anything when there is a new commit that just updates the documentation,
>> and the green red and grey buttons would show 0, 0, 0.  Is that what you
>> meant?
>>
>> > Not exactly. What I would be interested is to get a list of packages
> that
> > previous succeeded, and now they fail, and also a list of packages that
> were
> > failing, but now build.
>
>
>> Clément
>>
>
You do link the diff of each commit with the files that were impacted by
the change and must be re-evaluated?

[-- Attachment #2: Type: text/html, Size: 1997 bytes --]

  reply	other threads:[~2018-08-02 19:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 22:08 Web interface pushed Clément Lassieur
2018-07-29 23:46 ` Ludovic Courtès
2018-07-30 12:45   ` Pjotr Prins
2018-07-30 13:26     ` Ricardo Wurmus
2018-08-01 19:47       ` Tatiana Sholokhova
2018-08-02  6:53         ` Clément Lassieur
2018-08-02 16:00           ` Gábor Boskovits
2018-08-02 16:49             ` Clément Lassieur
2018-08-02 18:48               ` Gábor Boskovits
2018-08-02 19:21                 ` Amirouche Boubekki [this message]
2018-08-02 20:16                   ` Clément Lassieur
2018-08-02 18:13         ` Amirouche Boubekki
2018-08-02 20:17           ` Clément Lassieur
2018-08-03 13:53         ` Ricardo Wurmus
2018-08-04 21:53           ` Tatiana Sholokhova
2018-08-04 22:03             ` Ricardo Wurmus
2018-08-07 21:33               ` Tatiana Sholokhova
2018-08-09  9:17                 ` Clément Lassieur
2018-08-09 19:59                 ` amirouche
2018-08-09 20:46                 ` Ricardo Wurmus
2018-08-10  5:01                   ` Gábor Boskovits
2018-08-10  9:10                     ` Clément Lassieur
2018-08-11 16:38                       ` Ricardo Wurmus
2018-07-30  7:38 ` amirouche
2018-07-30  9:11   ` Clément Lassieur
2018-07-30  9:23     ` Alex Sassmannshausen
2018-07-30  9:41       ` Nils Gillmann
2018-07-30 12:08     ` Ricardo Wurmus
2018-07-30 12:14       ` Gábor Boskovits
2018-07-30 14:10     ` Hartmut Goebel
2018-07-30 16:02       ` Clément Lassieur
2018-07-30 18:43         ` Amirouche Boubekki

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL7_Mo-EM2UkmScMrXP6cGwxjYtZP3BtgVas274zgagWrACgNw@mail.gmail.com \
    --to=amirouche.boubekki@gmail.com \
    --cc=boskovits@gmail.com \
    --cc=clement@lassieur.org \
    --cc=guix-devel@gnu.org \
    --cc=tanja201396@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.