From: Richard Sent <richard@freakingpenguin.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 70202@debbugs.gnu.org
Subject: [bug#70202] [PATCH] doc: Add message for common error about make check-system
Date: Mon, 17 Jun 2024 08:13:03 -0400 [thread overview]
Message-ID: <87ed8v22eo.fsf@freakingpenguin.com> (raw)
In-Reply-To: <87tthrpz3n.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Mon, 17 Jun 2024 13:50:36 +0200")
Hi Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> Hello Richard, I am hesitant because I cannot reproduce the error and it
> might be better to fix it rather than document it. Looking at,
I can't reliably reproduce the error myself. It simply "comes up" every
now and then if I switch between branches with an existing build and try
rebuilding Guix and rerunning the tests. Agreed, a fix would be
preferred. I have absolutely no idea how.
> I do not understand Guix well enough why this could happen. Since `make
> clean-go` helps, the cause must be in Guix’ .go files and not some
> cache. In Makefile.am, the check-system target depends on $(GOBJECTS).
>
> I presume gnu/tests.go and gnu/ci.go should be added to GOBJECTS?
> Or gnu/tests.scm and gnu/ci.scm should be added to MODULES?
I don't believe the issue is limited to those two files in particular
(although it could be). That just happened to be the file causing the
problem when I caught the error and pasted it in the doc.
> But I do not really understand.
That makes two of us. :)
--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
prev parent reply other threads:[~2024-06-17 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 21:17 [bug#70202] [PATCH] doc: Add message for common error about make check-system Richard Sent
2024-06-17 11:50 ` pelzflorian (Florian Pelz)
2024-06-17 12:13 ` Richard Sent [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
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=87ed8v22eo.fsf@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=70202@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).