bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#15933: make check not working


From: Eli Zaretskii
Subject: bug#15933: make check not working
Date: Thu, 28 Nov 2013 21:46:21 +0200

> 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.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]