unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Ken Brown <kbrown@cornell.edu>
Cc: Andreas Politz <politza@hochschule-trier.de>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 716b468: Extend `file-notify-test02-rm-watch'
Date: Mon, 01 May 2017 20:45:15 +0200	[thread overview]
Message-ID: <87lgqgmn5w.fsf@detlef> (raw)
In-Reply-To: <c849d259-f90d-4cf7-5e21-b9a3fbff5bd5@cornell.edu> (Ken Brown's message of "Mon, 1 May 2017 14:28:24 -0400")

Ken Brown <kbrown@cornell.edu> writes:

> Hi Michael,

Hi Ken,

> On my systems I seem to need a much larger sit-for timeout (on the
> order of 0.1 or more rather than 0.001) in order for the test to pass.
> But maybe this is not worth worrying about, since it's clear that this
> is a timing issue rather than a file-notify problem.

I've moved the `sit-for' call to `file-notify--test-read-event' by
intention, so we have just one place to change. You could do something
like

(if (eq system-type 'cygwin)
  (sit-for 0.1 'nodisp))

The other backends do not need them as far as I'm aware of, so do it at
your convenience. Maybe also with a comment ...

>> One point still irritates me: the tests run under cygwin change the
>> results after a while. Several tests which pass after a reboot of a
>> machine, will fail when I use the machine for some hours. It isn't the
>> first time I've observed this, so I need to reboot my machine again and
>> again when working for cygwin.
>>
>> Do you know this behaviour?
>
> No, I don't see this.  I hardly ever reboot my computer.  But I mostly
> run 64-bit Cygwin.  Are you running 32-bit Cygwin?  And are the
> problems related to fork failures?  (You would see error messages to
> this effect on the terminal or in the logs.)  If so, I might be able
> to help.  But in that case we should probably continue the discussion
> off-list.

Likely 32-bit. But I use it very rarely, so I don't want to waste your
time with debugging when you don't know it from somewhere else.

> Regards,
>
> Ken

Best regards, Michael.



  reply	other threads:[~2017-05-01 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170322131610.22658.57119@vcs0.savannah.gnu.org>
     [not found] ` <20170322131611.5FF7D20E17@vcs0.savannah.gnu.org>
2017-04-04 22:36   ` [Emacs-diffs] master 716b468: Extend `file-notify-test02-rm-watch' Ken Brown
2017-04-05  6:58     ` Michael Albinus
2017-04-05 19:24       ` Ken Brown
2017-04-05 21:02     ` Andreas Politz
2017-04-06  2:59       ` Ken Brown
2017-04-07 14:56         ` Ken Brown
2017-05-01 10:21           ` Michael Albinus
2017-05-01 18:28             ` Ken Brown
2017-05-01 18:45               ` Michael Albinus [this message]
2017-05-08 13:28                 ` Ken Brown
2017-05-08 15:30                   ` Michael Albinus

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=87lgqgmn5w.fsf@detlef \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=kbrown@cornell.edu \
    --cc=politza@hochschule-trier.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).