From: Guillaume Le Vaillant <glv@posteo.net>
To: Greg Hogan <code@greghogan.com>
Cc: 73210@debbugs.gnu.org
Subject: [bug#73210] [PATCH] gnu: smalltalk: Fix tests.
Date: Fri, 13 Sep 2024 17:23:00 +0000 [thread overview]
Message-ID: <87v7yza2ob.fsf@kitej> (raw)
In-Reply-To: <CA+3U0ZnGWC9mwbQ7M7gLJycm_fBqdaJGor3HPx7O2rCXJ97ycg@mail.gmail.com> (Greg Hogan's message of "Fri, 13 Sep 2024 08:18:29 -0400")
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
Greg Hogan <code@greghogan.com> skribis:
> On Fri, Sep 13, 2024 at 5:59 AM Guillaume Le Vaillant <glv@posteo.net> wrote:
>>
>> Hi.
>> I tried your patch, but some tests are still failing for me.
>> More specifically, the "ANSI compliancy tests" are all failing with the
>> same error:
>>
>> [...]
>>
>> Does the build work for you every time?
>> What architecture are you using? I'm on x86-64 Guix system.
>
> I have built the package two more times without errors (though the
> output is non-deterministic). The only error I have seen was the I18N
> test failure before adding this locales patch.
>
> My system is x86-64 on a foreign distro.
Given that the patch is correct (adding a missing input), I applied it
as 22a34ea792ef0df15fd30d46f557b572c61d5404.
The build farm built it fine for i686, but on x86-64 it got the same
error as me (https://ci.guix.gnu.org/build/5765437/details).
A strange thing is that if I keep the files of the failed build (with
"guix build -K") and then run the tests by hand, they all succeed.
I wonder where the difference with what you get could come from...
What CPU does your machine have? And how much RAM?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2024-09-13 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 19:38 [bug#73210] [PATCH] gnu: smalltalk: Fix tests Greg Hogan
2024-09-13 9:59 ` Guillaume Le Vaillant
2024-09-13 12:18 ` Greg Hogan
2024-09-13 17:23 ` Guillaume Le Vaillant [this message]
2024-09-13 19:56 ` Greg Hogan
2024-09-14 9:12 ` bug#73210: " Guillaume Le Vaillant
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=87v7yza2ob.fsf@kitej \
--to=glv@posteo.net \
--cc=73210@debbugs.gnu.org \
--cc=code@greghogan.com \
/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).