From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62450@debbugs.gnu.org
Subject: bug#62450: 29.0.60; Skip failing tests on Cygwin with native compilation
Date: Sun, 26 Mar 2023 11:13:36 -0400 [thread overview]
Message-ID: <e470b0e6-c8d8-08dd-4a18-b22d127b4a07@cornell.edu> (raw)
In-Reply-To: <83mt3za7h9.fsf@gnu.org>
On 3/26/2023 10:54 AM, Eli Zaretskii wrote:
>> Date: Sun, 26 Mar 2023 10:15:17 -0400
>> Cc: 62450-done@debbugs.gnu.org
>> From: Ken Brown <kbrown@cornell.edu>
>> I've been building and running Emacs like this for a couple months and
>> not doing any rebasing, and I haven't seen a single fork failure outside
>> of the test suite. So this might be the way to handle the problem in
>> the long run.
>
> Feel free to install the above on master.
Good idea. That way maybe it will get some more testing. AFAIK, I'm
the only one who's tried this so far (at the suggestion of Corinna, the
Cygwin maintainer).
>> But I still hope to figure out what's different about native
>> compilation in the test suite.
>
> You mean, why the fork fails? I thought the PROBLEMS entry explains
> that?
No, I mean why ASLR doesn't prevent the fork failure in the test suite,
even though it prevents it while building Emacs and in my daily use of
Emacs. Or maybe a better question is whether my ASLR patch is actually
taking effect for the compilations done in the test suite. There has to
be something different going on there, but I don't know what.
Ken
prev parent reply other threads:[~2023-03-26 15:13 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
2023-03-26 14:15 ` Ken Brown
2023-03-26 14:54 ` Eli Zaretskii
2023-03-26 15:13 ` Ken Brown [this message]
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=e470b0e6-c8d8-08dd-4a18-b22d127b4a07@cornell.edu \
--to=kbrown@cornell.edu \
--cc=62450@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).