From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 15933@debbugs.gnu.org, andrewjmoreton@gmail.com
Subject: bug#15933: make check not working
Date: Mon, 25 Nov 2013 23:08:25 +0200 [thread overview]
Message-ID: <834n70b35i.fsf@gnu.org> (raw)
In-Reply-To: <874n70709f.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: andrewjmoreton@gmail.com, 15933@debbugs.gnu.org
> Date: Mon, 25 Nov 2013 20:24:28 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > --[make check]----------------------------------------------
> >> > Indenting module modname...done
> >> > passed 180/521 f90-test-bug8691
> >> > passed 181/521 f90-test-bug8820
> >> > passed 182/521 f90-test-bug9553a
> >> > passed 183/521 f90-test-bug9553b
> >> > passed 184/521 f90-test-bug9690
> >> > passed 185/521 f90-test-indent
> >> > passed 186/521 file-notify-test00-availability
> >> > skipped 187/521 file-notify-test00-availability-remote
> >> > passed 188/521 file-notify-test01-add-watch
> >> > skipped 189/521 file-notify-test01-add-watch-remote
> >> > make[1]: *** [check] Error 5
> >> > make[1]: Leaving directory `/c/emacs/src/emacs/trunk/obj-mingw32/test/automated'
> >> Oops. Please indicate in the bug report the environment you were
> >> using. I guess it was MS Windows whatever (which might it make hard for
> >> me to debug, 'cause I don't use it).
> >
> > It might be easy enough to guess why it fails. I see this in
> > file-notify-tests.el:
> >
> > ;; There is no default value on w32 systems, which could work out of the box.
> > (defconst file-notify-test-remote-temporary-file-directory
> > (if (eq system-type 'windows-nt) null-device "/ssh::/tmp")
> > "Temporary directory for Tramp tests.")
>
> No, it did fail in file-notify-test02-events.
How do you know? The fact that it said "skipped" does not necessarily
mean the code that "skipped" didn't error out.
If you do know what triggered the error, can you point it out?
> null-device is an indicator NOT to try remote test cases.
Why not nil?
> "/ssh::/tmp" is indeed for accessing a local sshd. Nothing I would
> assume for MS Windows.
You could provide for a possibility to set this up with a remote Unix
machine. It would be better than just skipping, I think.
next prev parent reply other threads:[~2013-11-25 21:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 12:55 bug#15933: make check not working Andy Moreton
2013-11-20 18:49 ` Glenn Morris
2013-11-20 18:56 ` Glenn Morris
2013-11-20 21:33 ` Eli Zaretskii
2013-11-21 0:34 ` Glenn Morris
2013-11-20 19:04 ` Eli Zaretskii
2013-11-20 19:10 ` Glenn Morris
2013-11-20 19:14 ` Glenn Morris
2013-11-20 21:38 ` Eli Zaretskii
2013-11-20 21:53 ` Eli Zaretskii
2013-11-21 0:33 ` Glenn Morris
2013-11-21 3:46 ` Eli Zaretskii
2013-11-20 21:34 ` Eli Zaretskii
2013-11-20 20:34 ` Andy Moreton
2013-11-21 0:36 ` Glenn Morris
2013-11-21 0:56 ` Andy Moreton
2013-11-24 14:36 ` Michael Albinus
2013-11-25 11:48 ` Andy Moreton
2013-11-25 12:31 ` Michael Albinus
2013-11-25 17:15 ` Eli Zaretskii
2013-11-25 19:24 ` Michael Albinus
2013-11-25 21:08 ` Eli Zaretskii [this message]
2013-11-25 21:30 ` Glenn Morris
2013-11-26 13:08 ` Michael Albinus
2013-11-26 13:13 ` Michael Albinus
2013-11-28 19:46 ` Eli Zaretskii
2013-11-28 20:28 ` Eli Zaretskii
2013-11-29 10:36 ` Eli Zaretskii
2013-11-29 10:22 ` Andy Moreton
2013-11-29 11:16 ` 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=834n70b35i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15933@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=michael.albinus@gmx.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.
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).