From debbugs-submit-bounces@debbugs.gnu.org Tue May 04 18:35:17 2021 Received: (at 46038) by debbugs.gnu.org; 4 May 2021 22:35:17 +0000 Received: from localhost ([127.0.0.1]:55833 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1le3dN-0000zq-0J for submit@debbugs.gnu.org; Tue, 04 May 2021 18:35:17 -0400 Received: from cascadia.aikidev.net ([173.255.214.101]:45574) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1le3dK-0000zi-Tw for 46038@debbugs.gnu.org; Tue, 04 May 2021 18:35:16 -0400 Received: from localhost (97-120-1-76.ptld.qwest.net [97.120.1.76]) (Authenticated sender: vagrant@aikidev.net) by cascadia.aikidev.net (Postfix) with ESMTPSA id D87A31A904; Tue, 4 May 2021 15:35:08 -0700 (PDT) From: Vagrant Cascadian To: Ludovic =?utf-8?Q?Court=C3=A8s?= Subject: Re: bug#46038: guix 1.3.0rc1 test failure: channels-news, one entry In-Reply-To: <875yzymg1h.fsf@gnu.org> References: <87lfck6hbl.fsf@yucca> <87bl9tvppm.fsf@yucca> <875yzymg1h.fsf@gnu.org> Date: Tue, 04 May 2021 15:34:44 -0700 Message-ID: <871ramt9ff.fsf@yucca> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 46038 Cc: 46038@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2021-05-04, Ludovic Court=C3=A8s wrote: > Vagrant Cascadian skribis: > >> On 2021-01-22, Vagrant Cascadian wrote: >>> I've uploaded guix 1.2.0 built against guile-2.2 to Debian, and while it >>> builds fine on the official buildd.debian.org infrastructure, on amd64 >>> and arm64 the "channel-news, one entry" test from tests/channels.scm >>> fails on tests.reproducible-builds.org. >>> >>> There are likely a few differences in the two build environments, >>> possibly including network access. >>> >>> Does the "channel-news, one entry" test indirectly depend on network or >>> bootstrap binaries? >>> >>> Could a difference in locale related variables affect the result of the >>> test (e.g. LANGUAGE=3Den:en_US vs. LANGUAGE unset, LC_ALL unset >>> vs. LC_ALL=3DC or LC_ALL=3DC.UTF-8)? >>> >>> https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd6= 4/guix.html >> >> Still basically the same story with 1.3.0rc1, in some cases this test >> fails, but I haven't consistently figured out what triggers it. >> >> >>> test-name: channel-news, one entry >>> location: /build/1st/guix-1.2.0/tests/channels.scm:324 >>> source: > > [...] > >>> + (lset=3D equal? >>> + (map channel-news-entry-title >>> + (channel-news-for-commit channel commit5)) >>> + '((("en" . "Another file!")) >>> + (("en" . "Old news.") ("eo" . "Malnova?oj.")))) > > The culprit is right here: it should read =E2=80=9CMalnova=C4=B5oj=E2=80= =9D, but there=E2=80=99s a > question mark instead of =E2=80=98=C4=B5=E2=80=99. > > Could it be that you=E2=80=99re not running tests in a UTF-8 locale? Thanks for taking a deeper look! Yes, on tests.reproducible-builds.org, one build is run in the C locale, the other in various UTF-8 locales (somewhat arbitrarily tied to architecture exactly which UTF-8 locale is used). I'm guessing buildd.debian.org use C.UTF-8, since it builds fine there. So now the question is what to do; should tests be able to assume a UTF-8 locale? Should I try to adapt the test to work in C? Should I workaround it in the Debian packaging by forcing to use a UTF-8 locale (on Debian, the only one definitely available is C.UTF-8, which isn't in upstream glibc, and thus not in guix itself). live well, vagrant --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYJHMBAAKCRDcUY/If5cW qqQDAP9kMwfAOx1eDo/+OGZydmkGRjDxwHkSAM9htT3Fhb7f/wEA9sWmJj8hMmuE BjjFH33rWIzeofrSHZ0I+moziOEbAQo= =L1QL -----END PGP SIGNATURE----- --=-=-=--