From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Getting ‘core-updates’ merged
Date: Mon, 26 Nov 2018 18:54:50 +0100 [thread overview]
Message-ID: <20181126185450.157efd52@alma-ubu> (raw)
In-Reply-To: <875zwpcuu0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
On Thu, 22 Nov 2018 10:41:59 +0100
ludo@gnu.org (Ludovic Courtès) wrote:
> There are still failures out there!
>
> https://hydra.gnu.org/eval/110331?full=1#tabs-still-fail
>
> The above list is slightly outdated so I’m restarting an evaluation on
> hydra.gnu.org.
You can also compare it to master, I think this gives a better picture
than comparing two consecutive core-updates evaluations:
https://hydra.gnu.org/eval/110331?compare=master#tabs-now-fail
(Update evaluation-number when a newer evaluation is finished)
It's also worth looking at the "New jobs" tab, as new jobs can
initially fail and version-updates are handled as
old-version-out-new-version-in.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-11-26 17:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 8:28 New release soon? swedebugia
2018-11-14 11:44 ` Ricardo Wurmus
2018-11-14 17:57 ` Marius Bakke
2018-11-16 18:10 ` Ludovic Courtès
2018-11-16 21:15 ` Ricardo Wurmus
2018-11-16 21:20 ` Ludovic Courtès
2018-11-16 22:03 ` Björn Höfling
2018-11-17 0:58 ` Gábor Boskovits
2018-11-17 14:14 ` Getting ‘core-updates’ merged Ludovic Courtès
2018-11-22 9:41 ` Ludovic Courtès
2018-11-22 19:54 ` Björn Höfling
2018-11-23 13:52 ` Ludovic Courtès
2018-11-23 21:44 ` Julien Lepiller
2018-11-24 9:19 ` Danny Milosavljevic
2018-11-25 15:54 ` Ludovic Courtès
2018-11-26 17:59 ` Danny Milosavljevic
2018-11-26 18:18 ` Danny Milosavljevic
2018-11-28 10:46 ` Ludovic Courtès
2018-11-26 17:54 ` Björn Höfling [this message]
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=20181126185450.157efd52@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.