From: Pieter van Oostrum <pieter-l@vanoostrum.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 39075@debbugs.gnu.org
Subject: bug#39075: 28.0.50; Emacs hangs on 100% CPU and grows beyond bounds in shell-mode
Date: Sun, 19 Jan 2020 22:41:22 +0100 [thread overview]
Message-ID: <lxh80rcef1.fsf@cochabamba.vanoostrum.org> (raw)
In-Reply-To: <vq8sm3b9jq.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 19 Jan 2020 13:11:53 -0500")
Glenn Morris <rgm@gnu.org> writes:
> Pieter van Oostrum wrote:
>
>> I propose to amend the test also, so that it would have caught this
>> error (by hanging).
>
> I haven't read anything else, so take this with a grain of salt, but
> tests that hang (rather than just fail) are a PITA for automated testing.
That is true, but the test is there to test the fix, which makes it no longer hang. And as these are in the same commit, the test should never hang, unless somebody breaks the fix later. But then hanging could occur with any bug.
--
Pieter van Oostrum
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]
next prev parent reply other threads:[~2020-01-19 21:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 21:16 bug#39075: 28.0.50; Emacs hangs on 100% CPU and grows beyond bounds in shell-mode Pieter van Oostrum
2020-01-11 9:59 ` Eli Zaretskii
2020-01-12 17:11 ` Pieter van Oostrum
2020-01-12 17:43 ` Eli Zaretskii
2020-01-13 13:58 ` Pieter van Oostrum
2020-01-15 3:17 ` Michael Welsh Duggan
2020-01-15 19:15 ` Pieter van Oostrum
2020-01-16 19:21 ` Pieter van Oostrum
2020-01-18 9:57 ` Eli Zaretskii
2020-01-19 18:08 ` Glenn Morris
2020-01-20 0:29 ` Pieter van Oostrum
2020-01-17 10:57 ` Pieter van Oostrum
2020-01-19 18:11 ` Glenn Morris
2020-01-19 21:41 ` Pieter van Oostrum [this message]
2020-01-20 7:47 ` Michael Albinus
2020-01-20 13:12 ` Pieter van Oostrum
2020-01-20 13:33 ` Michael Albinus
2020-01-20 14:57 ` Mattias Engdegård
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=lxh80rcef1.fsf@cochabamba.vanoostrum.org \
--to=pieter-l@vanoostrum.org \
--cc=39075@debbugs.gnu.org \
--cc=rgm@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).