From: ludo@gnu.org (Ludovic Courtès)
To: Eli Zaretskii <eliz@gnu.org>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel@gnu.org
Subject: Re: Strange UNRESOLVED results in elisp-compiler.test
Date: Wed, 02 Jul 2014 12:00:22 +0200 [thread overview]
Message-ID: <871tu4ytah.fsf@gnu.org> (raw)
In-Reply-To: <83y4we4efs.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Jun 2014 18:14:47 +0300")
Eli Zaretskii <eliz@gnu.org> skribis:
> These UNRESOLVED results in elisp-compiler.test puzzle me:
>
> UNRESOLVED: elisp-compiler.test: Exceptions: catch and throw
> UNRESOLVED: elisp-compiler.test: Exceptions: unwind-protect
> UNRESOLVED: elisp-compiler.test: Equivalence Predicates: eq
>
> Any idea why could these fail on Windows? Where do I find their
> implementation that needs to be examined for the reasons?
I don’t know why, but we’re seeing the same on GNU/Linux, so no worries.
Ludo’.
next prev parent reply other threads:[~2014-07-02 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 15:14 Strange UNRESOLVED results in elisp-compiler.test Eli Zaretskii
2014-07-02 10:00 ` Ludovic Courtès [this message]
2014-07-02 14:48 ` Eli Zaretskii
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=871tu4ytah.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=eliz@gnu.org \
--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).