unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 64760@debbugs.gnu.org
Subject: bug#64760: make check fails on 182be30fb1a8b847c30492462ec22c08ec7a9849
Date: Sun, 30 Jul 2023 18:19:40 +0200	[thread overview]
Message-ID: <874jllcqxv.fsf_-_@gnu.org> (raw)
In-Reply-To: <873518m8zr.fsf@jpoiret.xyz> (Josselin Poiret's message of "Fri,  28 Jul 2023 16:00:24 +0200")

Josselin Poiret writes:

Hey!

> Janneke Nieuwenhuizen <janneke@gnu.org> writes:
>
>> Just a headsup that this change breaks the store-roots test on the hurd
>> for me.
>
> Thanks for the feedback Janneke.  It seems that there is some left-over
> state that can mess with this state's result: I was initially surprised
> that the /profiles directory could appear in the gc roots, but that's
> because it is symlinked under /gcroots, not because it is itself
> searched for gc roots.
>
> In any case, the /gcroots directory along with the /gcroots/profiles
> symlink is created when a connection is made to the daemon, which is not
> the case here yet.  However, a connection might have been opened before
> for the same state dir (which depends on the PID of
> build-aux/test-env.in).  It might also depend on whether the clean-up of
> the state directory made by `trap` worked and whether PIDs get re-used
> quickly on the specific kernel.  I think this is all too unreliable
> here (I have one such example of a leftover PID state dir in my tree, so
> it might happen more often than not).

Yes, that could be.  I've got another data-point for i686-linux (see
also https://issues.guix.gnu.org/64959); the package and texlive tests
now pass, and store-roots is made to fail like so:

--8<---------------cut here---------------start------------->8---
test-name: gc-roots, initial
location: /home/janneke/src/guix/wip-i686/tests/store-roots.scm:33
source:
+ (test-equal
+   "gc-roots, initial"
+   '()
+   (begin
+     (false-if-exception
+       (delete-file-recursively
+         (string-append %state-directory "/profiles")))
+     (gc-roots)))
expected-value: ()
actual-value: ("/home/janneke/src/guix/wip-i686/test-tmp/var/30690/profiles")
result: FAIL
--8<---------------cut here---------------end--------------->8---

> In any case, if this test is only here to check if gc-roots doesn't
> error out, we could return #t at the end to only fish for errors.  WDYT?

(good question.../me passes insights here to "others" ;)

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com




  reply	other threads:[~2023-07-30 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  6:47 bug#64760: make check fails on 182be30fb1a8b847c30492462ec22c08ec7a9849 Janneke Nieuwenhuizen
2023-07-21 10:12 ` Josselin Poiret via Bug reports for GNU Guix
2023-07-21 10:14   ` bug#64760: [PATCH 1/3] tests: packages: Set system for expected result of package->bag Josselin Poiret via Bug reports for GNU Guix
2023-07-21 10:14   ` bug#64760: [PATCH 2/3] tests: store-roots: Initial gc-roots should be empty Josselin Poiret via Bug reports for GNU Guix
2023-07-28  8:52     ` Janneke Nieuwenhuizen
2023-07-28 11:58       ` Janneke Nieuwenhuizen
2023-07-28 14:00       ` Josselin Poiret via Bug reports for GNU Guix
2023-07-30 16:19         ` Janneke Nieuwenhuizen [this message]
2023-07-21 10:14   ` bug#64760: [PATCH 3/3] tests: texlive: Remove texlive-texworks from propagated-inputs Josselin Poiret via Bug reports for GNU Guix
2023-08-18 14:13     ` bug#64760: make check fails on 182be30fb1a8b847c30492462ec22c08ec7a9849 Ludovic Courtès
2023-07-21 11:17   ` Janneke Nieuwenhuizen
2023-08-09 21:41 ` Ludovic Courtès
2023-08-11 12:31   ` Janneke Nieuwenhuizen

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=874jllcqxv.fsf_-_@gnu.org \
    --to=janneke@gnu.org \
    --cc=64760@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=ludo@gnu.org \
    /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).