From: Michael Albinus <michael.albinus@gmx.de>
To: Pieter van Oostrum <pieter-l@vanoostrum.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: Mon, 20 Jan 2020 08:47:11 +0100 [thread overview]
Message-ID: <87h80q1se8.fsf@gmx.de> (raw)
In-Reply-To: <lxh80rcef1.fsf@cochabamba.vanoostrum.org> (Pieter van Oostrum's message of "Sun, 19 Jan 2020 22:41:22 +0100")
Pieter van Oostrum <pieter-l@vanoostrum.org> writes:
>>> 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.
I haven't checked your test case, but in Tramp I try to avoid hanging by
wrapping process related tests with a timer.
Experience has taught me, that I'm able to break the tests all the time
by new code :-(
Best regards, Michael.
next prev parent reply other threads:[~2020-01-20 7:47 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
2020-01-20 7:47 ` Michael Albinus [this message]
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=87h80q1se8.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=39075@debbugs.gnu.org \
--cc=pieter-l@vanoostrum.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).