all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andreas Enge <andreas@enge.fr>, guix-devel@gnu.org
Subject: Re: Latest news on core-updates
Date: Fri, 21 Apr 2023 10:20:18 +0200	[thread overview]
Message-ID: <861qkd63zx.fsf@gmail.com> (raw)
In-Reply-To: <ZD/HBwNBoSp1jFcC@jurong>

Hi Andreas,

On Wed, 19 Apr 2023 at 12:48, Andreas Enge <andreas@enge.fr> wrote:

> I hope we will be able to merge core-updates after next weekend; also for
> personal reasons, since I will not be able to spend much time on it any
> more after that.

I do not know if something is twisted with the report [1] of Cuirass but
many things seems missing.  Right?

Therefore, if many things are still missing, I suggest to apply #62967
[2].  It removes the annoyance you spotted out in #62954 [3].  And as I
explained in [4], it will be safe because ’valgrind’ appears only in the
testsuite of ’lz4’ and ’valgrind’ is not even run there.

Doing so, it will fix failures for powerpc64le and will increase the
coverage.

WDYT?


1: https://ci.guix.gnu.org/eval/417699/dashboard
2: https://issues.guix.gnu.org/62967
3 https://issues.guix.gnu.org/62954
4: https://issues.guix.gnu.org/62954#3


Moreover, I have revamped the GHC bootstrap chain.

 1. it cuts the number of Haskell compilers to build,
 2. it separates building the compiler itself and running the testsuite,
 3. it introduces ghc-toolchain that glue one compiler and its testsuite.

Well, #2 removing failure for i686 [5] since the failure of the
testsuite of 8.10.7 is not blocking for 9.2.5.

However, the patches needs more polishing and then because of ’pandoc’
depending on the GHC bootstrap, it would a large rebuild.

Since Haskell is also broken on master for i686, I guess the option is
to apply on some “feature™ branch” after the merge, right?


5: https://ci.guix.gnu.org/build/953241/details

Cheers,
simon


  parent reply	other threads:[~2023-04-21  8:21 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57   ` Andreas Enge
2023-04-17  8:06     ` Andreas Enge
2023-04-17  8:18 ` Core-updates after the staging merge Guillaume Le Vaillant
2023-04-17  8:33   ` Andreas Enge
2023-04-17  9:03 ` Andreas Enge
2023-04-17  9:56   ` Andreas Enge
2023-04-17 12:19     ` Simon Tournier
2023-04-17 12:38       ` Andreas Enge
2023-04-17 12:57         ` Simon Tournier
2023-04-17 14:12       ` Lars-Dominik Braun
2023-04-17 17:47         ` Simon Tournier
2023-04-17 18:07           ` Andreas Enge
2023-04-17 19:01             ` Lars-Dominik Braun
2023-04-18 17:16               ` Andreas Enge
2023-04-21 18:29                 ` Lars-Dominik Braun
2023-04-17 12:57   ` Andreas Enge
2023-04-17 18:03   ` Maxim Cournoyer
2023-04-17 18:08     ` Andreas Enge
2023-04-18  5:04   ` John Kehayias
2023-04-18 17:38     ` Andreas Enge
2023-04-19 10:48   ` Latest news on core-updates Andreas Enge
2023-04-19 10:58     ` Christopher Baines
2023-04-19 12:41       ` Andreas Enge
2023-04-21  7:58         ` Andreas Enge
2023-04-21 13:01           ` Maxim Cournoyer
2023-04-20 13:56       ` Christopher Baines
2023-04-20 18:09         ` Andreas Enge
2023-04-21  8:20     ` Simon Tournier [this message]
2023-04-21  8:47       ` Andreas Enge
2023-04-21 11:31         ` Simon Tournier
2023-04-21 16:12     ` Katherine Cox-Buday
2023-04-21 16:12       ` Katherine Cox-Buday
2023-04-21 17:04       ` reza.housseini
2023-04-23  7:17         ` Andreas Enge

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=861qkd63zx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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.