From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 15933@debbugs.gnu.org
Subject: bug#15933: make check not working
Date: Thu, 28 Nov 2013 21:46:21 +0200 [thread overview]
Message-ID: <83r4a08g36.fsf@gnu.org> (raw)
In-Reply-To: <vz1fvqkd7np.fsf@gmail.com>
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Mon, 25 Nov 2013 11:48:10 +0000
>
> The log from my most recent run of 'make check' ended with:
>
> --[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'
> --[make check]----------------------------------------------
>
> I haven't got any further looking into this as the machine I was using
> died last week...
Please try again when you can. This was actually a crash (didn't you
see a popup asking whether to debug or close the application?), due to
the fact that w32 file notifications, as implemented, did not support
batch mode of operation -- they relied on machinery that is only up
and running in interactive sessions. This should be fixed as of trunk
revision 115269.
The other part of the puzzle was that auto-revert-stop-on-user-input
should be bound to nil when running the rest of the tests in
file-notify-tests.el, but Michael already fixed that part earlier
today.
There are still a few (6 on one machine, 3 on another) tests that fail
on Windows, but there are no more crashes.
next prev parent reply other threads:[~2013-11-28 19:46 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r4a08g36.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15933@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.