From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master updated (5af5ed6c62 -> f07505d1ec)
Date: Wed, 07 Sep 2022 13:46:21 +0200 [thread overview]
Message-ID: <874jxjpfua.fsf@gnus.org> (raw)
In-Reply-To: <563857da-1467-4181-1c69-dcf4c968314b@gmail.com> (Jim Porter's message of "Tue, 6 Sep 2022 15:46:46 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
> Hmm, in that case, I think my patch would be hiding a real bug (though
> possibly just a bug in that test). I'll see if I can force it to fail
> locally, or failing that, we can mark it unstable. I think that would
> be better than working around the bug in the test...
Yup.
In the last run on EMBA, that test didn't fail, but this one did:
Test esh-proc-test/sigpipe-exits-process condition:
(ert-test-failed
((should
(eq
(process-list)
nil))
:form
(eq
(#<process sh-stderr>)
nil)
:value nil))
FAILED 16/16 esh-proc-test/sigpipe-exits-process (1.013610 sec) at lisp/eshell/esh-proc-tests.el:122
Ran 16 tests, 14 results as expected, 1 unexpected, 1 skipped (2022-09-07 10:27:03+0000, 2.594968 sec)
1 unexpected results:
FAILED esh-proc-test/sigpipe-exits-process ((should (eq
(process-list) nil)) :form (eq (#<process sh-stderr>) nil) :value
nil)
Also native-comp.
https://emba.gnu.org/emacs/emacs/-/jobs/53405
next prev parent reply other threads:[~2022-09-07 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166233264971.21612.17042094685015365861@vcs2.savannah.gnu.org>
2022-09-05 0:17 ` master updated (5af5ed6c62 -> f07505d1ec) Lars Ingebrigtsen
2022-09-05 0:18 ` Lars Ingebrigtsen
2022-09-05 0:22 ` Lars Ingebrigtsen
2022-09-05 0:25 ` Jim Porter
2022-09-06 9:33 ` Lars Ingebrigtsen
2022-09-06 18:41 ` Jim Porter
2022-09-06 20:13 ` Lars Ingebrigtsen
2022-09-06 22:46 ` Jim Porter
2022-09-07 11:46 ` Lars Ingebrigtsen [this message]
2022-09-07 21:03 ` Jim Porter
2022-09-08 12:02 ` Lars Ingebrigtsen
2022-09-08 22:16 ` 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=874jxjpfua.fsf@gnus.org \
--to=larsi@gnus.org \
--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 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.