From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 62450@debbugs.gnu.org
Subject: bug#62450: 29.0.60; Skip failing tests on Cygwin with native compilation
Date: Sun, 26 Mar 2023 07:44:52 +0300 [thread overview]
Message-ID: <835yaoazp7.fsf@gnu.org> (raw)
In-Reply-To: <519b122a-a46c-0abd-6bc8-a4dc64f869ac@cornell.edu> (message from Ken Brown on Sat, 25 Mar 2023 16:55:49 -0400)
> Date: Sat, 25 Mar 2023 16:55:49 -0400
> From: Ken Brown <kbrown@cornell.edu>
>
> When 'make check' is run on Cygwin and Emacs has been built with native
> compilation, all the tests in comp-tests.el and benchmark-tests.el fail
> with fork errors, for the reasons explained in etc/PROBLEMS. I don't
> see an easy way to fix this by rebasing, as is done elsewhere in the
> code, and I don't think it's worth investing any effort into this just
> for the sake of making some tests pass. I propose that we just skip
> these tests.
>
> Patch attached (with a placeholder for the bug number). OK for emacs-29?
OK, but please add in both places comments explaining the reason, and
in particular include there a pointer to etc/PROBLEMS.
(I do wonder whether this is a good idea in the long run. Native
compilation is here to stay, so avoiding its testing for Cygwin might
not be the best solution. The PROBLEMS entry seems to imply that
relatively simple measures, which the test suite could take, could
avoid the fork failures, so my recommendation would be to try to find
a better fix in the future, albeit not in Emacs 29.)
next prev parent reply other threads:[~2023-03-26 4:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 20:55 bug#62450: 29.0.60; Skip failing tests on Cygwin with native compilation Ken Brown
2023-03-26 4:44 ` Eli Zaretskii [this message]
2023-03-26 14:15 ` Ken Brown
2023-03-26 14:54 ` Eli Zaretskii
2023-03-26 15:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835yaoazp7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62450@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 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.