From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: 62954@debbugs.gnu.org
Subject: bug#62954: Valgrind blocks R on powerpc64le
Date: Fri, 21 Apr 2023 09:59:37 +0200 [thread overview]
Message-ID: <86fs8t64ye.fsf@gmail.com> (raw)
In-Reply-To: <ZEFuldg6prmdzkAX@jurong>
Hi,
On Thu, 20 Apr 2023 at 18:55, Andreas Enge <andreas@enge.fr> wrote:
> Am Thu, Apr 20, 2023 at 03:25:17PM +0200 schrieb Simon Tournier:
>> See #62967 [1] for an attempt. I am rebuilding to detect the potential problem.
>
> Not sure why we need a second issue... All this should work, let us wait
> till after the core-updates merge.
Because it is two “mailing lists“ under the hood: guix-patches and bug-guix.
As someone who digs (time to time, and not enough these days, oups!) to
“forgotten” issues, I find easier to follow the discussion about one
specific bug and the discussion about one specific implementation
when they are separated – somehow it reduces the “noise”.
Well, for example consider #58650 [1]. It is time-consuming to know if
the PATCH is “forgotten“ or if it does not fix the issue and can be
dropped.
Moreover, the two patches of #58650 [1] does not appear if you follow
only guix-patches; because the issue had not been marked +patch.
Speaking about “forgotten” issues, #62967 (patch) does not mention
#62954 (bug) and that is a kind of “mistake”, I agree. :-)
Last, on the pragmatic side, I do not know if the CI is following
bug-guix and if it tries to extract patches from it. (Yes, for this
case it is not relevant; the patch is dropped by CI because it implies
more rebuilds than the threshold.)
Well, it’s a matter of taste. :-)
1: https://issues.guix.gnu.org/issue/58650
Cheers,
simon
next prev parent reply other threads:[~2023-04-21 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 20:08 bug#62954: Valgrind blocks R on powerpc64le Andreas Enge
2023-04-20 11:26 ` Simon Tournier
2023-04-20 11:50 ` Andreas Enge
2023-04-20 12:35 ` Simon Tournier
2023-04-20 13:25 ` Simon Tournier
2023-04-20 16:55 ` Andreas Enge
2023-04-21 7:59 ` Simon Tournier [this message]
2023-04-21 8:37 ` Andreas Enge
2023-04-25 15:24 ` 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
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=86fs8t64ye.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=62954@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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).