From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vagrant Cascadian <vagrant@debian.org>
Subject: bug#40650: =?UTF-8?Q?=E2=80=98scandir*=E2=80=99?= test failure
Date: Sat, 18 Apr 2020 13:19:30 -0700
Message-ID: <87eeskeect.fsf@ponder>
References: <87pnc8wgnq.fsf@yucca> <87d087kem6.fsf@gnu.org>
 <87o8rr1h02.fsf@ponder> <87mu7abinc.fsf@gnu.org> <87sgh14v6y.fsf@yucca>
 <87ftd0604z.fsf_-_@gnu.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
 micalg=pgp-sha512; protocol="application/pgp-signature"
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:48608)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1jPtwZ-0006yf-1d
 for bug-guix@gnu.org; Sat, 18 Apr 2020 16:20:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1jPtwY-0000VY-EM
 for bug-guix@gnu.org; Sat, 18 Apr 2020 16:20:02 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:60336)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
 (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1jPtwY-0000Uq-1j
 for bug-guix@gnu.org; Sat, 18 Apr 2020 16:20:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1jPtwX-0003EF-Sa
 for bug-guix@gnu.org; Sat, 18 Apr 2020 16:20:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.40650.B40650.158724118512382@debbugs.gnu.org>
In-Reply-To: <87ftd0604z.fsf_-_@gnu.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: 40650@debbugs.gnu.org

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 2020-04-18, Ludovic Court=C3=A8s 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 =E2=80=98every=E2=80=99 could return #=
f is (1) if
> =E2=80=98lstat=E2=80=99 returns a different inode number, or (2) if =E2=
=80=98lstat=E2=80=99 returns a
> different file type than the one for =E2=80=98scandir*=E2=80=99.

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?


> Unfortunately it=E2=80=99s hard to tell more without debugging interactiv=
ely on
> the machine, adding =E2=80=98pk=E2=80=99 calls here and there to see.
>
> Can you reproduce this test failure in a simpler environment when
> interactive debugging is possible?

Yeah, I could build in a one-off chroot or virtual machine using a
"normal" filesystem.


live well,
  vagrant

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCXptg1AAKCRDcUY/If5cW
qhJxAQCIGXyxzCwnJUgi5Nq/UtqhWFT8n9J3KBa96TwhqpTTzgD/V+V4vC1rZF+V
trO4cDAdxe7DYL5YCud9srqTwPbRLQE=
=T0J4
-----END PGP SIGNATURE-----
--=-=-=--