From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Bytecompiler test fails
Date: Mon, 22 Jun 2015 07:21:54 +0200 [thread overview]
Message-ID: <CAFgFV9N9S-a2H0r8VtAyJE0ZfBwyDoHnhv5uS2FvM1fbqB7S4w@mail.gmail.com> (raw)
In-Reply-To: <834mm0ihft.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
2015-06-22 4:51 GMT+02:00 Eli Zaretskii <eliz@gnu.org>:
> > From: Fabrice Popineau <fabrice.popineau@gmail.com>
> > Date: Sun, 21 Jun 2015 23:20:50 +0200
> > Cc: Emacs developers <emacs-devel@gnu.org>
> >
> > lI still have 3 failures:
> >
> > SUMMARY OF TEST RESULTS
> > -----------------------
> > Files examined: 75
> > Ran 1467 tests, 1381 results as expected, 8 unexpected, 78 skipped
> > 3 files contained unexpected results:
> > vc-tests.log
> > package-test.log
> > ert-x-tests.log
>
> What's the problem with vc-test? Do you have RCS installed, and does
> it crash? If so, I'm working on that (the problem seems to be in RCS).
>
>
This command is expected to fail in test/automated/vs-tests.el:133:
(shell-command-to-string (format "cvs -Q -d:local:%s co module" tmp-dir))
because tmp-dir is a windows path, aka c:/Users/.../temp .
I have an msys2/rcs installed:
$ pacman -Q rcs
rcs 5.9.4-1
$ pacman -Q cvs
cvs 1.11.23-2
But if I'm right, being an msys2 rcs/cvs, they don't support native win32
path syntax.
Fabrice
[-- Attachment #2: Type: text/html, Size: 1892 bytes --]
next prev parent reply other threads:[~2015-06-22 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:49 Bytecompiler test fails Fabrice Popineau
2015-06-21 17:30 ` Eli Zaretskii
2015-06-21 21:20 ` Fabrice Popineau
2015-06-22 2:51 ` Eli Zaretskii
2015-06-22 5:21 ` Fabrice Popineau [this message]
2015-06-22 15:05 ` Eli Zaretskii
2015-06-27 11:30 ` 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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFgFV9N9S-a2H0r8VtAyJE0ZfBwyDoHnhv5uS2FvM1fbqB7S4w@mail.gmail.com \
--to=fabrice.popineau@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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/emacs.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).