all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54136@debbugs.gnu.org, Jim Porter <jporterbugs@gmail.com>
Subject: bug#54136: 29.0.50; Eshell emits extra prompts when killing processes in some cases
Date: Thu, 24 Feb 2022 21:07:29 +0100	[thread overview]
Message-ID: <87ee3s111a.fsf@gnus.org> (raw)
In-Reply-To: <83tucoqbfr.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Feb 2022 22:03:36 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> OK, so I installed my changes.

The test now fails on Debian:

Test esh-proc-test/kill-pipeline condition:
    (ert-test-failed
     ((should
       (equal
	(buffer-substring-no-properties output-start ...)
	(or "interrupt\n" "killed\n")))
      :form
      (equal "killed\n" "interrupt\n")
      :value nil :explanation
      (arrays-of-different-length 7 10 "killed\n" "interrupt\n" first-mismatch-at 0)))
   FAILED  2/4  esh-proc-test/kill-pipeline (0.109668 sec) at lisp/eshell/esh-proc-tests.el:47
   passed  3/4  esh-proc-test/kill-pipeline-head (0.112142 sec)
   passed  4/4  esh-proc-test/sigpipe-exits-process (1.010359 sec)

Ran 4 tests, 3 results as expected, 1 unexpected (2022-02-24 21:06:48+0100, 1.446135 sec)

1 unexpected results:
   FAILED  esh-proc-test/kill-pipeline

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-02-24 20:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  5:11 bug#54136: 29.0.50; Eshell emits extra prompts when killing processes in some cases Jim Porter
2022-02-24  5:16 ` Jim Porter
2022-02-24  9:35   ` Lars Ingebrigtsen
2022-02-24 11:03     ` Eli Zaretskii
2022-02-24 18:55       ` Jim Porter
2022-02-24 20:03         ` Eli Zaretskii
2022-02-24 20:07           ` Lars Ingebrigtsen [this message]
2022-02-25  1:04             ` Jim Porter
2022-02-25  2:18               ` Lars Ingebrigtsen
2022-02-25  7:09               ` Eli Zaretskii
2022-02-25 18:31                 ` Jim Porter

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ee3s111a.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=54136@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jporterbugs@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.