From: Jack Hill <jackhill@jackhill.us>
To: 42726@debbugs.gnu.org
Subject: bug#42726: bigloo 4.3f test fail
Date: Wed, 5 Aug 2020 20:10:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2008052006050.4809@marsh.hcoop.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Hi Guix,
Some of bigloo's 4.3f's tests fail. I'm using Guix commit
05f3d34094b23dc9612ff6641a0257bc4f7dcd12.
The failing tests appear to be
bignum.scm:
58.bignum(bignum.34) fail: provided [#f], wanted [#t]
59.bignum(bignum.35) fail: provided [#f], wanted [#t]
60.bignum(bignum.36) fail: provided [#f], wanted [#t]
and
eval.scm:
recette failed: 3 error(s) occurred.inline.scm:
The full build log is attatched.
Best,
Jack
[-- Attachment #2: bigloo build log --]
[-- Type: application/octet-stream, Size: 740232 bytes --]
next reply other threads:[~2020-08-06 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 0:10 Jack Hill [this message]
2021-04-29 13:24 ` bug#42726: bigloo 4.3f test fail 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=alpine.DEB.2.21.2008052006050.4809@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=42726@debbugs.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).