unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: 73765@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#73765] Request for merging "meson-enable-parallel-tests" branch
Date: Thu, 28 Nov 2024 05:43:05 +0000	[thread overview]
Message-ID: <87bjxzsyl6.fsf_-_@protonmail.com> (raw)
In-Reply-To: <87msj9opbn.fsf@gmail.com>

Hello,

On Wed, Nov 27, 2024 at 11:52 AM, GNU bug Tracking System wrote:

> Your bug report
>
> #73765: Request for merging "meson-enable-parallel-tests" branch
>
> which was filed against the guix-patches package, has been closed.
>
> The explanation is attached below, along with your original report.
> If you require more details, please reply to 73765@debbugs.gnu.org.
>
> --
> 73765: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=73765
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
>
> From: Andreas Enge <andreas@enge.fr>
> Subject: Re: bug#73765: Request for merging "meson-enable-parallel-tests"
>  branch
> To: Ludovic Courtès <ludo@gnu.org>
> Cc: 73765-done@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
> Date: Wed, 27 Nov 2024 12:51:30 +0100 (17 hours, 46 minutes, 36 seconds ago)
>
> 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
>

I just noticed the big build queue on Cuirass, is that all for the
non-x86_64 architectures? (The change to mesa, if it was on the branch
before, is ~4k packages alone). Should we have waited for that to
get up to reasonable coverage before pushing to master?

PS: Andreas I saw some messages earlier in this thread that again didn't
go to others. Annoyingly, the debbugs bug number address doesn't go to
anyone (that I know of) and I've frequently missed or miss-sent messages
because of that. Just thought I'd let you know in case you missed that.

Thanks for everyone's work on this!
John

>
> ----------
>
> From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
> Subject: Request for merging "meson-enable-parallel-tests" branch
> To: guix-patches <guix-patches@gnu.org>
> Date: Sat, 12 Oct 2024 14:36:12 +0900
> Date: Sat, 12 Oct 2024 14:36:12 +0900 (6 weeks, 5 days, 1 minute ago)
>
> Hi,
>
> This was fully built for x86_64 as some insurance that it didn't
> introduce any problem:
> https://ci.guix.gnu.org/jobset/meson-parallel-tests
>
> It's ready to me merged.





  parent reply	other threads:[~2024-11-28  5:44 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     ` bug#73765: " Andreas Enge
2024-11-28  6:27     ` [bug#73765] " Maxim Cournoyer
2024-11-28  5:43 ` John Kehayias via Guix-patches via [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87bjxzsyl6.fsf_-_@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=73765@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=john.kehayias@protonmail.com \
    --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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).