unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jan Synacek <jsynacek@redhat.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: Guile 2.0.6 - some tests fail
Date: Mon, 08 Oct 2012 08:40:48 +0200	[thread overview]
Message-ID: <50727570.5070108@redhat.com> (raw)
In-Reply-To: <871uhbna3a.fsf@tines.lan>

On 10/06/2012 12:55 PM, Mark H Weaver wrote:
> Jan Synacek <jsynacek@redhat.com> writes:
>> when I run 'make check', some guile tests fail and I'm not sure why [1, 2].
>>
>> [1] http://jsynacek.fedorapeople.org/guile/check-guile.log
>> [2] http://jsynacek.fedorapeople.org/guile/check-guile-fails.log (only FAILs)
> 
> Quoting from [2] (but rearranging the order somewhat):
> 
>> XFAIL: chars.test: basic char handling: comparisons: char=? #\A #\a
>> XFAIL: chars.test: basic char handling: comparisons: char=? #\A #\B
>> XFAIL: chars.test: basic char handling: comparisons: char=? #\B #\A
>> XFAIL: chars.test: basic char handling: comparisons: char<? #\A #\A
>> XFAIL: chars.test: basic char handling: comparisons: char<? #\B #\A
>> XFAIL: chars.test: basic char handling: comparisons: char<=? #\B #\A
>> XFAIL: chars.test: basic char handling: comparisons: char>? #\A #\A
>> XFAIL: chars.test: basic char handling: comparisons: char>? #\A #\a
>> XFAIL: chars.test: basic char handling: comparisons: char>? #\A #\B
>> XFAIL: chars.test: basic char handling: comparisons: char>=? #\A #\a
>> XFAIL: chars.test: basic char handling: comparisons: char>=? #\A #\B
>> XFAIL: chars.test: basic char handling: comparisons: char-ci=? #\A #\B
>> XFAIL: chars.test: basic char handling: comparisons: char-ci=? #\B #\A
>> XFAIL: chars.test: basic char handling: comparisons: char-ci<? #\A #\A
>> XFAIL: chars.test: basic char handling: comparisons: char-ci<? #\A #\a
>> XFAIL: chars.test: basic char handling: comparisons: char-ci<? #\B #\A
>> XFAIL: chars.test: basic char handling: comparisons: char-ci<=? #\B #\A
>> XFAIL: chars.test: basic char handling: comparisons: char-ci>? #\A #\A
>> XFAIL: chars.test: basic char handling: comparisons: char-ci>? #\A #\a
>> XFAIL: chars.test: basic char handling: comparisons: char-ci>? #\A #\B
>> XFAIL: chars.test: basic char handling: comparisons: char-ci>=? #\A #\B
> 
> These are not failures in Guile itself, but rather inappropriate uses of
> 'expect-fail' in test cases where #f is the expected result.  You
> needn't worry about them, and I have fixed these test cases on the
> stable-2.0 branch.
> 
>> XFAIL: eval.test: map: documented?
>> XFAIL: eval.test: define set procedure-name: procedure-with-setter
>> XFAIL: goops.test: defining classes: define-class: bad init-thunk
>> XFAIL: list.test: append!: wrong argument: improper list and empty list
>> XFAIL: list.test: append!: wrong argument: improper list and list
>> XFAIL: list.test: append!: wrong argument: list, improper list and list
>> XFAIL: list.test: append!: wrong argument: circular list and empty list
>> XFAIL: list.test: append!: wrong argument: circular list and list
>> XFAIL: list.test: append!: wrong argument: list, circular list and list
> 
> These are expected failures, i.e. reminders to Guile developers to
> improve the implementation.  I just fixed the first three 'append!'
> cases (checking for improper lists) on the stable-2.0 branch, and will
> look into fixing the others at some point, but you needn't worry about
> them.
> 
>> FAIL: ftw.test: file-system-fold: test-suite (never enter)
>> FAIL: ftw.test: file-system-fold: test-suite/lib.scm (flat file)
>> FAIL: ftw.test: scandir: no select
>> FAIL: ports.test: %file-port-name-canonicalization: absolute canonicalization from ice-9
> 
> These are genuine problems that most users haven't run into AFAIK, and
> we should try to find the underlying cause.  Obviously they are all
> filesystem related, so the first question that comes to mind is: What
> filesystem type is your Guile source directory stored on?  Can you think
> of anything else unusual about your system that might affect filesystem
> behavior?
> 
> Thanks very much for bringing these problems to our attention.
> 
>      Mark
> 

Thank you for your answer.

I'm running ext4 on an LVM partition. No acls, no funky file permissions. I've
also tried turning selinux off, but that didn't help. I've gathered some
additional info about my filesystem [3]. Other than that, I can't think of
anything else that could be wrong/special in any way. If there's more info that
you need, just let me know.

[3] http://jsynacek.fedorapeople.org/guile/fs.info

Thank you,
-- 
Jan Synacek
Software Engineer, BaseOS team Brno, Red Hat



  reply	other threads:[~2012-10-08  6:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04  9:12 Guile 2.0.6 - some tests fail Jan Synacek
2012-10-06 10:55 ` Mark H Weaver
2012-10-08  6:40   ` Jan Synacek [this message]
2012-10-09 21:40   ` Ludovic Courtès
2012-10-09 21:41   ` Ludovic Courtès
2012-10-11  8:43     ` Jan Synacek
2012-10-11 12:43       ` Mark H Weaver
2012-10-15  7:56         ` Jan Synacek
2012-10-15  8:17     ` Jan Synacek
2012-10-16 14:28       ` Ludovic Courtès
2012-10-17  6:16         ` Jan Synacek
2012-10-17 13:45           ` Ludovic Courtès

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=50727570.5070108@redhat.com \
    --to=jsynacek@redhat.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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.
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).