From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: 25605@debbugs.gnu.org, 25606@debbugs.gnu.org
Subject: bug#25605: bug#25606: patches installed for 25605, 25606
Date: Tue, 07 Feb 2017 21:47:42 +0000 [thread overview]
Message-ID: <CAArVCkTya-az6CRSPPhHMa5VPrk9kUXke7g-Chh6sDP3=56-Lg@mail.gmail.com> (raw)
In-Reply-To: <42bf63df-416e-7623-8f59-862fbd55f2f3@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am Di., 7. Feb. 2017 um 17:32 Uhr:
> On 02/07/2017 04:47 AM, Philipp Stephani wrote:
> > If they fail, shouldn't the test runner that runs these tests time out
> > after some time and mark them as failures?
>
> Not if the test runner is written in elisp. The loops are deep in the C
> code and are immune to elisp timeouts. (I don't know how the test runner
> works.)
>
>
How about running the Emacs binary wrapped in /usr/bin/timeout?
[-- Attachment #2: Type: text/html, Size: 932 bytes --]
next prev parent reply other threads:[~2017-02-07 21:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 23:56 bug#25605: [DRAFT PATCH 1/2] Simplify use of FOR_EACH_TAIL Paul Eggert
2017-02-01 23:56 ` bug#25606: [DRAFT PATCH 2/2] Signal list cycles in ‘length’ etc Paul Eggert
2017-02-02 17:28 ` Eli Zaretskii
2017-02-02 23:01 ` Paul Eggert
2017-02-03 7:55 ` Eli Zaretskii
2017-02-03 20:29 ` Paul Eggert
2017-02-04 9:05 ` Eli Zaretskii
2017-02-04 19:11 ` Paul Eggert
2017-02-04 19:52 ` Eli Zaretskii
2017-02-04 21:45 ` Paul Eggert
2017-02-05 18:45 ` Eli Zaretskii
2017-02-05 21:17 ` Paul Eggert
2017-02-02 17:29 ` bug#25605: [DRAFT PATCH 1/2] Simplify use of FOR_EACH_TAIL Eli Zaretskii
2017-02-05 21:30 ` bug#25605: patches installed for 25605, 25606 Paul Eggert
2017-02-06 16:04 ` bug#25605: bug#25606: " Eli Zaretskii
2017-02-07 6:53 ` Paul Eggert
2017-02-07 12:47 ` Philipp Stephani
2017-02-07 16:32 ` bug#25605: " Paul Eggert
2017-02-07 21:47 ` Philipp Stephani [this message]
2017-02-07 22:20 ` Paul Eggert
2017-02-07 22:55 ` Philipp Stephani
2017-02-10 9:59 ` bug#25605: " Eli Zaretskii
2017-02-12 8:31 ` Paul Eggert
2017-02-12 16:13 ` bug#25605: " Eli Zaretskii
2017-02-12 18:55 ` Paul Eggert
2017-02-12 19:33 ` Eli Zaretskii
2017-02-12 19:41 ` bug#25605: " Lars Ingebrigtsen
2017-02-12 19:49 ` bug#25606: " Lars Ingebrigtsen
2017-02-12 20:22 ` Eli Zaretskii
2017-02-12 19:43 ` Paul Eggert
2017-02-13 9:11 ` Michael Albinus
2017-02-13 14:37 ` Eli Zaretskii
2017-02-12 19:41 ` Eli Zaretskii
2017-02-12 20:57 ` bug#25605: " Paul Eggert
2017-02-13 5:37 ` Eli Zaretskii
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='CAArVCkTya-az6CRSPPhHMa5VPrk9kUXke7g-Chh6sDP3=56-Lg@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=25605@debbugs.gnu.org \
--cc=25606@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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).