From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 73765-done@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#73765: Request for merging "meson-enable-parallel-tests" branch
Date: Wed, 27 Nov 2024 12:51:30 +0100 [thread overview]
Message-ID: <Z0cHwqtLrHh_P_pX@jurong> (raw)
In-Reply-To: <87jzcpapl0.fsf_-_@gnu.org>
Hello!
I have gone back to the original merge request and noticed, following
Maxim's remark, that indeed no build failures occurred. Updating the meson
version resulted in build failures, but which looked more like random test
failures in somewhat brittle packages that fail on and off.
So I have taken the liberty and rebased on master and pushed.
I had forgotten that the branch was not yet built on i686, sorry.
Apart from that, I think it is good to clear the space for the following
branches waiting in line.
Andreas
next prev parent reply other threads:[~2024-11-27 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 5:36 [bug#73765] Request for merging "meson-enable-parallel-tests" branch Maxim Cournoyer
2024-10-15 9:26 ` Christopher Baines
2024-10-29 0:19 ` Maxim Cournoyer
2024-11-22 12:59 ` [bug#73765] Rebased Andreas Enge
2024-11-22 14:45 ` [bug#73765] Request for merging "meson-enable-parallel-tests" branch Ludovic Courtès
2024-11-22 15:03 ` Andreas Enge
2024-11-22 15:27 ` Andreas Enge
2024-11-25 8:39 ` [bug#73765] Results Andreas Enge
2024-11-26 17:10 ` [bug#73765] Request for merging "meson-enable-parallel-tests" branch Ludovic Courtès
2024-11-27 11:51 ` Andreas Enge [this message]
2024-11-28 6:27 ` Maxim Cournoyer
2024-11-28 5:43 ` John Kehayias via Guix-patches via
2024-11-28 7:46 ` Maxim Cournoyer
2024-11-28 8:51 ` Andreas Enge
2024-11-28 15:37 ` John Kehayias via Guix-patches via
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=Z0cHwqtLrHh_P_pX@jurong \
--to=andreas@enge.fr \
--cc=73765-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@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.