From: Andy Wingo <wingo@pobox.com>
To: "Alexander Shendi" <Alexander.Shendi@web.de>
Cc: 21891@debbugs.gnu.org
Subject: bug#21891: Guile 2.1.1: 5 Test failures on OpenBSD/amd64 5.8
Date: Fri, 24 Jun 2016 18:11:54 +0200 [thread overview]
Message-ID: <87eg7mefcl.fsf@pobox.com> (raw)
In-Reply-To: <trinity-9c6c9197-edc7-43be-b0da-81c5371bdec9-1447348244257@3capp-webde-bs05> (Alexander Shendi's message of "Thu, 12 Nov 2015 18:10:44 +0100")
On Thu 12 Nov 2015 18:10, "Alexander Shendi" <Alexander.Shendi@web.de> writes:
> I have built guile-2.1.1 on OpenBSD/amd64 5.8. I did the following:
>
> The build itself went smoothly and the system seems to work, but the generated "check-guile.log" shows
> 5 errors. I do not have enough guile-foo to deceide if the failures are serious or not.
Cool, thank you very much for testing the release!
These are the five failures, for what it's worth:
FAIL: i18n.test: locale objects: make-locale with unknown locale
FAIL: i18n.test: character mapping: char-locale-upcase Turkish
FAIL: i18n.test: character mapping: char-locale-downcase Turkish
FAIL: i18n.test: string mapping: string-locale-upcase Turkish
FAIL: i18n.test: string mapping: string-locale-downcase Turkish
They are not terribly serious. I guess that you get them on Guile
2.0.11 as well. Is that the case?
The last 4 could a problem with OpenBSD's iconv for turkish locales; not
sure. I don't know about the first one.
Andy
prev parent reply other threads:[~2016-06-24 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 17:10 bug#21891: Guile 2.1.1: 5 Test failures on OpenBSD/amd64 5.8 Alexander Shendi
2016-06-24 16:11 ` Andy Wingo [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg7mefcl.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=21891@debbugs.gnu.org \
--cc=Alexander.Shendi@web.de \
/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.
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).