From: Vin Shelton <acs@alumni.princeton.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Test Failures
Date: Wed, 28 Oct 2020 09:59:48 -0400 [thread overview]
Message-ID: <CACeGjnU-9TsEAae=45SZ2bycji8JW6b1dWUGYSK++XK3j-wfaw@mail.gmail.com> (raw)
In-Reply-To: <87r1piwym8.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
I can confirm that the python-shell failures are gone. Thanks, Larsi.
FYI, on an unrelated note, I'm seeing five failures when BLDDIR != SRCDIR:
FAILED xref-elisp-test-find-defs-defgeneric-el
FAILED xref-elisp-test-find-defs-defun-defvar-el
FAILED xref-elisp-test-find-defs-defun-el
FAILED xref-elisp-test-find-defs-defvar-el
FAILED xref-elisp-test-find-defs-feature-el
HTH,
Vin
On Wed, Oct 28, 2020 at 4:20 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Vin Shelton <acs@alumni.princeton.edu> writes:
>
> > 3 unexpected results:
> > FAILED python-shell-buffer-substring-10
> > FAILED python-shell-buffer-substring-11
> > FAILED python-shell-buffer-substring-12
>
> Should be fixed now.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 2091 bytes --]
next prev parent reply other threads:[~2020-10-28 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 3:00 Test Failures Vin Shelton
2020-10-28 8:20 ` Lars Ingebrigtsen
2020-10-28 13:59 ` Vin Shelton [this message]
2020-10-29 2:30 ` Dmitry Gutov
-- strict thread matches above, loose matches on Subject: below --
2020-08-21 20:23 test failures Stephen Berman
2020-08-21 20:36 ` Lars Ingebrigtsen
2020-08-21 20:45 ` Stephen Berman
2020-08-22 11:32 ` Stephen Berman
2020-08-22 6:31 ` Eli Zaretskii
2014-07-15 3:29 Test failures Nick Dokos
2014-07-15 7:44 ` Achim Gratz
2014-07-27 13:43 ` Bastien
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='CACeGjnU-9TsEAae=45SZ2bycji8JW6b1dWUGYSK++XK3j-wfaw@mail.gmail.com' \
--to=acs@alumni.princeton.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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.