[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#15933: make check not working
From: |
Michael Albinus |
Subject: |
bug#15933: make check not working |
Date: |
Mon, 25 Nov 2013 20:24:28 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
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. No remote access.
file-notify-test02-events-remote would be skipped, like
file-notify-test00-availability-remote and
file-notify-test01-add-watch-remote above.
> How is this supposed to work? null-device is not a directory. I'm
> guessing that "Error 5" is "access denied" emitted by Windows because
> some file primitive tries to treat null-device as if it were a
> directory.
null-device is an indicator NOT to try remote test cases.
> If you could explain what you intended to achieve by that, perhaps I
> could suggest a solution. (Does "/ssh::/tmp" assume there's an sshd
> running on the machine that runs the tests?)
"/ssh::/tmp" is indeed for accessing a local sshd. Nothing I would
assume for MS Windows.
Best regards, Michael.
bug#15933: make check not working, Andy Moreton, 2013/11/20
- bug#15933: make check not working, Glenn Morris, 2013/11/20
- bug#15933: make check not working, Andy Moreton, 2013/11/20
- bug#15933: make check not working, Michael Albinus, 2013/11/24
- bug#15933: make check not working, Andy Moreton, 2013/11/25
- bug#15933: make check not working, Michael Albinus, 2013/11/25
- bug#15933: make check not working, Eli Zaretskii, 2013/11/25
- bug#15933: make check not working,
Michael Albinus <=
- bug#15933: make check not working, Eli Zaretskii, 2013/11/25
- bug#15933: make check not working, Glenn Morris, 2013/11/25
- bug#15933: make check not working, Michael Albinus, 2013/11/26
bug#15933: make check not working, Michael Albinus, 2013/11/26
bug#15933: make check not working, Eli Zaretskii, 2013/11/28
bug#15933: make check not working, Eli Zaretskii, 2013/11/28
bug#15933: make check not working, Eli Zaretskii, 2013/11/29
bug#15933: make check not working, Andy Moreton, 2013/11/29
bug#15933: make check not working, Eli Zaretskii, 2013/11/29