unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: Philipp Stephani <phst@google.com>,
	Michael Albinus <michael.albinus@gmx.de>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 16bb108: Add a regression test for Bug#24325.
Date: Mon, 04 Jan 2021 18:24:23 +0100	[thread overview]
Message-ID: <87czyk39a0.fsf@gmail.com> (raw)
In-Reply-To: <CAArVCkRBNMJQOogKtRZkWcax1z5GAHSM_Luh9B1eO9TyxCQNeA@mail.gmail.com> (Philipp Stephani's message of "Tue, 29 Dec 2020 19:10:55 +0100")

Philipp Stephani <p.stephani2@gmail.com> writes:

> Am Di., 29. Dez. 2020 um 18:56 Uhr schrieb Michael Albinus
> <michael.albinus@gmx.de>:
>>
>> p.stephani2@gmail.com (Philipp Stephani) writes:
>>
>> Hi Philipp,
>>
>> > +(ert-deftest process-tests/fd-setsize-no-crash ()
>> > +  "Check that Emacs doesn't crash when trying to use more than
>> > +FD_SETSIZE file descriptors (Bug#24325)."
>> > +  (let ((sleep (executable-find "sleep"))
>> > +        ;; FD_SETSIZE is typically 1024 on Unix-like systems.
>> > +        (fd-setsize 1024)
>>
>> This could be determined by "ulimit -n" or "getconf OPEN_MAX".
>>
>
> That's a different limit (resource limit vs. size of a file descriptor set).

Itʼs possible to raise FD_SETSIZE at compile time on macOS (to 4096 if
memory serves), so the only reliable way to test this is to expose
FD_SETSIZE to lisp. poll(2) anyone? ;-)

Robert



      reply	other threads:[~2021-01-04 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201229172038.13382.38744@vcs0.savannah.gnu.org>
     [not found] ` <20201229172040.85BB72094D@vcs0.savannah.gnu.org>
2020-12-29 17:55   ` master 16bb108: Add a regression test for Bug#24325 Michael Albinus
2020-12-29 18:10     ` Philipp Stephani
2021-01-04 17:24       ` Robert Pluim [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=87czyk39a0.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=p.stephani2@gmail.com \
    --cc=phst@google.com \
    /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).