all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roman Scherer <roman@burningswell.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 60037-done@debbugs.gnu.org
Subject: [bug#60037] Update CDO to 2.1.0 and add libaec and eccodes
Date: Tue, 20 Dec 2022 09:32:15 +0100	[thread overview]
Message-ID: <CAEc_D2_DJkJksFkPMfpvRzKmj1C402VKOOS0iix6dUFfQgOEpg@mail.gmail.com> (raw)
In-Reply-To: <87y1r3nskf.fsf@kitej>

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

Nice. Thank you!

On Mon, Dec 19, 2022, 19:42 Guillaume Le Vaillant <glv@posteo.net> wrote:

> Roman Scherer <roman.scherer@burningswell.com> skribis:
>
> >
> > Hi Guillaume,
> >
> > thanks for looking at this patch series and sorry for the trouble. I
> > just rebuild the patch series on top of the current master 3 times with
> > the following command:
> >
> > ```
> > ./pre-inst-env guix build --check --no-grafts --no-substitutes
> --rounds=3 cdo
> > ```
> >
> > I see some tests are skipped, but the whole thing passed every time. I
> > also don't remember seeing them failing a single time.
> >
> > I'm running this on the following system:
> >
> > ```
> > Linux precision 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC
> 2022 x86_64 x86_64 x86_64 GNU/Linux
> > ```
> >
> > And here are the logs of one of the test runs:
> >
> > [...]
> >
> > On what kind of system is this failing for you? What can we do?
>
> On my main machine, with an AMD Ryzen 9 CPU with 32 threads, it failed
> every time. On another machine, with an Intel I9 CPU with 16 threads, it
> succeeded every time. It turns out that some tests can fail if the
> machine has many threads, and adding '#:parallel-tests? #f' to the
> 'arguments' field fixes the issue.
>
> I also changed the 'source' field of the libaec package to use
> 'git-fetch' instead of 'url-fetch', because archive files created
> automatically by forges like gitlab can sometimes change in place and
> have a different hash.
>
> Patches pushed as d03b6fb0e3f0b81b35a9b35b89c213c144c59fe6 and
> following. Thanks.
>

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

      reply	other threads:[~2022-12-20  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 17:52 [bug#60037] Update CDO to 2.1.0 and add libaec and eccodes Roman Scherer
2022-12-19 14:43 ` Guillaume Le Vaillant
2022-12-19 16:24   ` Roman Scherer
2022-12-19 18:31     ` bug#60037: " Guillaume Le Vaillant
2022-12-20  8:32       ` Roman Scherer [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=CAEc_D2_DJkJksFkPMfpvRzKmj1C402VKOOS0iix6dUFfQgOEpg@mail.gmail.com \
    --to=roman@burningswell.com \
    --cc=60037-done@debbugs.gnu.org \
    --cc=glv@posteo.net \
    /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.