From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: emacs-devel@gnu.org
Cc: Jim Porter <jporterbugs@gmail.com>
Subject: "make lisp/eshell/esh-proc-tests" fails intermittently since 7e50861ca7ed3f620fe62ac6572f6e88b3600ece
Date: Sun, 24 Sep 2023 20:39:21 +0200 [thread overview]
Message-ID: <ea8d365a-f014-d4d7-14d0-60ccdfe7974e@vodafonemail.de> (raw)
Not sure whether anybody has seen or reported already: Approx. 1 of 5
executions of "make lisp/eshell/esh-proc-tests" fail for me like this:
------------------------- snip -------------------------
make[1]: Entering directory '/home/jschmidt/work/emacs-master/test'
GEN lisp/eshell/esh-proc-tests.log
Running 23 tests (2023-09-24 20:32:11+0200, selector `(not (tag :unstable))')
Loading em-alias...
Loading em-banner...
Loading em-basic...
Loading em-cmpl...
Loading em-extpipe...
Loading em-glob...
Loading em-hist...
Loading em-ls...
Loading em-pred...
Loading em-prompt...
Loading em-script...
Loading em-term...
Loading em-unix...
passed 1/23 esh-proc-test/exit-status/failure (0.117111 sec)
passed 2/23 esh-proc-test/exit-status/success (0.105469 sec)
passed 3/23 esh-proc-test/exit-status/with-stderr-pipe (0.105925 sec)
passed 4/23 esh-proc-test/kill-pipeline (0.108324 sec)
passed 5/23 esh-proc-test/kill-pipeline-head (0.108148 sec)
passed 6/23 esh-proc-test/kill-process/background-prompt (0.005315 sec)
[sleep]+ Done (/usr/bin/sleep 100)
passed 7/23 esh-proc-test/kill-process/foreground-only (0.207743 sec)
passed 8/23 esh-proc-test/kill-process/redirect-message (0.004864 sec)
Tramp: Sending command `exec sh -i'
Tramp: Found remote shell prompt on `sappc2'
Tramp: Sending command `exec sh -i'
Tramp: Found remote shell prompt on `sappc2'
passed 9/23 esh-proc-test/output/remote-redirect (0.157058 sec)
passed 10/23 esh-proc-test/output/stderr-to-buffer (0.106075 sec)
passed 11/23 esh-proc-test/output/stdout-and-stderr-to-buffer (0.105911 sec)
passed 12/23 esh-proc-test/output/stdout-to-buffer (0.105907 sec)
passed 13/23 esh-proc-test/output/to-screen (0.105792 sec)
passed 14/23 esh-proc-test/pipeline-connection-type/first (0.055700 sec)
passed 15/23 esh-proc-test/pipeline-connection-type/last (0.056159 sec)
make[1]: *** [Makefile:181: lisp/eshell/esh-proc-tests.log] Broken pipe
make[1]: Leaving directory '/home/jschmidt/work/emacs-master/test'
make: *** [Makefile:247: lisp/eshell/esh-proc-tests] Error 2
------------------------- snip -------------------------
I bisected with
------------------------- snip -------------------------
#!/bin/bash
make FAST=true -j8 bootstrap || exit 1
for (( i = 0; i < 30; i++ )); do
( cd test && make lisp/eshell/esh-proc-tests ) || exit 1
done
exit 0
------------------------- snip -------------------------
to
------------------------- snip -------------------------
7e50861ca7ed3f620fe62ac6572f6e88b3600ece is the first bad commit
commit 7e50861ca7ed3f620fe62ac6572f6e88b3600ece
Author: Jim Porter <jporterbugs@gmail.com>
Date: Thu Sep 14 17:51:16 2023 -0700
; Simplify how to use 'eshell-debug-command'
Now, 'eshell-debug-command' works more like 'format-message', which is
how we usually use it.
* lisp/eshell/esh-util.el (eshell-always-debug-command): New function.
(eshell-debug-command): Simplify. Update callers.
lisp/eshell/esh-arg.el | 6 +++---
lisp/eshell/esh-cmd.el | 10 ++++++----
lisp/eshell/esh-proc.el | 41 +++++++++++++++++------------------------
lisp/eshell/esh-util.el | 26 +++++++++++++++++---------
4 files changed, 43 insertions(+), 40 deletions(-)
bisect run success
------------------------- snip -------------------------
Pls let me know whether I should open a separate bug for this.
next reply other threads:[~2023-09-24 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 18:39 Jens Schmidt [this message]
2023-09-24 19:47 ` "make lisp/eshell/esh-proc-tests" fails intermittently since 7e50861ca7ed3f620fe62ac6572f6e88b3600ece Jim Porter
2023-09-24 20:13 ` Stefan Kangas
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=ea8d365a-f014-d4d7-14d0-60ccdfe7974e@vodafonemail.de \
--to=jschmidt4gnu@vodafonemail.de \
--cc=emacs-devel@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 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).