unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <Michael.Albinus@gmx.de>
To: Ken Brown <kbrown@cornell.edu>
Cc: 49665@debbugs.gnu.org
Subject: bug#49665: 28.0.50; Failing autorevert tests on Cygwin
Date: Tue, 20 Jul 2021 19:37:16 +0200	[thread overview]
Message-ID: <87mtqg999v.fsf@gmx.de> (raw)
In-Reply-To: <4da0123d-7719-9168-8944-9d8e6750a56a@cornell.edu> (Ken Brown's message of "Tue, 20 Jul 2021 12:26:51 -0400")

Ken Brown <kbrown@cornell.edu> writes:

Hi Ken,

> Some of the autorevert tests fail on Cygwin.  The precise tests that
> fail aren't the same in every run, but here's the result of the most
> recent run on my 64-bit Cygwin system:

[...]

> I'm not interested in spending a lot of time on this (or asking anyone
> else to spend time on it), because I've never seen a Cygwin user
> complain about auto-revert mode.  (Maybe no one uses it because it's
> slow.)  But I would like to stop seeing the test failures.
>
> Here's one possibility: Skip test02 and test05 on Cygwin, with a FIXME
> comment indicating that they've been failing for a long time and we
> don't know why.  Tag test00, test01, and test03 as expensive on Cygwin,
> since we would have to make the tests much slower in order for them to
> pass.  I'm not sure about test07.
>
> Other suggestions?

We have the tag :unstable for such tests. You might tag all tests you're
not interested in. Something like this after the docstring:

     :tags (when (eq system-type 'cygwin) '(:unstable))

Perhaps also a comment.

If you could provide me a recent Emacs 28 for cygwin, I could try to
check what's up.

> Thanks.
>
> Ken

Best regards, Michael.





  reply	other threads:[~2021-07-20 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 16:26 bug#49665: 28.0.50; Failing autorevert tests on Cygwin Ken Brown
2021-07-20 17:37 ` Michael Albinus [this message]
2021-07-20 20:15   ` Ken Brown
2021-07-20 21:23     ` Michael Albinus
2021-07-27 17:47       ` Michael Albinus
2021-07-28 11:48         ` Ken Brown

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=87mtqg999v.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=49665@debbugs.gnu.org \
    --cc=kbrown@cornell.edu \
    /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).