Re: Emacs master, w32/w64

[Fabrice Popineau <fabrice.popineau@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

2015-12-21 22:42 GMT+01:00 Michael Albinus <michael.albinus@gmx.de>:

> Fabrice Popineau <fabrice.popineau@gmail.com> writes:
>
> > At the moment, when I ran tests on emacs master build with msys2 on
> > w64,
> > filenotify-tests take forever long : 15mn on a core i7. I have the
> > feeling something is wrong with read_event / timeouts. I don't
> > remember something like this was happening before.
> >
> > Any idea where to look for to fix this ?
>
> Modify n in `file-notify-test06-many-events' to be a smaller number, or
> disable that test entirely. It is expected that this test runs for a
> while. However, when I have tried this last time (some weeks ago), I
> don't remember that all tests in filenotify.el took 15mn.
>
> Looking into `file-notify--test-timeout', the timeout for "w32notify" is
> much larger than the other timeouts. Likely it was me who has declared
> this long timeout, but I don't remember the details. It could be a sign
> that we have there problems, indeed.
>
>
Thanks for the quick answer. I can see that now.

However :

- both `file-notify-test02-events' and `file-notify-test06-many-events'
fail (with nil instead of the expected value)
- I have the feeling that the read-event calls do not timeout in 0.1s as
expected. When I run file-notify-test02-events
  in edebug mode, read-event does not return in less than 5-10s. I don't
know it is meaningful however.

I'll try to investigate, but I'm not familiar at all with the way all of
this is working.

Fabrice


> > Best regards,
> >
> > Fabrice
>
> Best regards, Michael.
>

[-- Attachment #2: Type: text/html, Size: 2568 bytes --]