From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 40650@debbugs.gnu.org
Subject: bug#40650: ‘scandir*’ test failure
Date: Sun, 19 Apr 2020 13:01:11 +0200 [thread overview]
Message-ID: <878sir4u4o.fsf@gnu.org> (raw)
In-Reply-To: <87eeskeect.fsf@ponder> (Vagrant Cascadian's message of "Sat, 18 Apr 2020 13:19:30 -0700")
Hello,
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2020-04-18, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@debian.org> skribis:
>>
>>> test-name: scandir*, properties
>>> location: /build/guix-YPdZIs/guix-1.1.0/tests/syscalls.scm:257
>>> source:
> ...
>> Looking at this test, the only way ‘every’ could return #f is (1) if
>> ‘lstat’ returns a different inode number, or (2) if ‘lstat’ returns a
>> different file type than the one for ‘scandir*’.
>
> My debian package builds are done using a overlay fs(with tmpfs on top,
> and ext4 below), which might explain inode discrepancies... this sort of
> thing is not uncommon in Debian package building environments.
>
> If that's indeed triggering the issue, maybe it needs some sort of
> workaround or a way to detect if it should skip the test?
Oh, I see. We would need to see exactly what the discrepancy is (is it
the inode number? for all the entries?), and from there we can come up
with a way to adjust the test or skip it.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-04-19 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 22:03 bug#40650: guix test suite failures building Debian package Vagrant Cascadian
2020-04-16 8:40 ` Ludovic Courtès
2020-04-16 17:23 ` Vagrant Cascadian
2020-04-17 8:50 ` Ludovic Courtès
2020-04-17 22:13 ` Vagrant Cascadian
2020-04-18 19:53 ` bug#40650: ‘scandir*’ test failure Ludovic Courtès
2020-04-18 20:19 ` Vagrant Cascadian
2020-04-19 11:01 ` Ludovic Courtès [this message]
2020-04-18 20:00 ` bug#40650: guix test suite failures building Debian package Ludovic Courtès
2020-04-18 20:02 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sir4u4o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40650@debbugs.gnu.org \
--cc=vagrant@debian.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.