unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan <stefan-guix@vodafonemail.de>
To: "Ludovic Courtès" <ludo@gnu.org>, 41654@debbugs.gnu.org
Subject: bug#41654: test-name: verify-store + check-contents failing on guix-1.2.0rc2-1.0d4b1af
Date: Wed, 30 Dec 2020 14:50:16 +0100	[thread overview]
Message-ID: <708455FD-2A6C-4E6C-8F2C-D2E5549F5886@vodafonemail.de> (raw)
In-Reply-To: <E447536D-56DB-4B72-BBDE-0E78A835B6F5@vodafonemail.de>

Hi Ludo’!

Could you please take a look at the bug report <https://issues.guix.gnu.org/41654>?

There are two reproducible problems when building the guix-1.2.0 package. 

There is a patch already for the first of the two problems (an incomplete cleanup) at <https://issues.guix.gnu.org/41654#2>.

For the other issue with a wrong path "dtmp/guix-tests/store/", there is a summary at <https://issues.guix.gnu.org/41654#3>. This problem is existing since years and seems to be depending on the underlying file-system. It seems to appear with a tmp-store on a unionfs-fuse or NFS. In the past it got hidden by switching to overlayfs or changes on the NFS server side. 

As the CI for aarch64 is always lagging behind these issues are kind of blockers to me. Today they block the build of guix-1.2.0-8.7624ebb.


Bye

Stefan





  reply	other threads:[~2020-12-30 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 23:14 bug#41654: Test of guix-1.1.0-4.bdc801e is failing on aarch64 Stefan
     [not found] ` <handler.41654.B.159105326917443.ack@debbugs.gnu.org>
2020-11-23  8:35   ` bug#41654: Acknowledgement (Test of guix-1.1.0-4.bdc801e is failing on aarch64) Stefan
2020-11-23  8:38     ` bug#41654: [PATCH] tests: Ignoring incomplete clean-up on NFS share Stefan
2020-11-23  9:20     ` bug#41654: test-name: verify-store + check-contents failing on guix-1.2.0rc2-1.0d4b1af Stefan
2020-12-30 13:50       ` Stefan [this message]
2021-01-04  1:05         ` Stefan

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=708455FD-2A6C-4E6C-8F2C-D2E5549F5886@vodafonemail.de \
    --to=stefan-guix@vodafonemail.de \
    --cc=41654@debbugs.gnu.org \
    --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).