From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 60626@debbugs.gnu.org
Subject: bug#60626: 30.0.50; `buffer-live-p' sometimes returns t on killed buffers
Date: Sat, 07 Jan 2023 15:42:19 +0200 [thread overview]
Message-ID: <83ilhisbpg.fsf@gnu.org> (raw)
In-Reply-To: <87v8lildj4.fsf@localhost> (message from Ihor Radchenko on Sat, 07 Jan 2023 12:44:47 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Sat, 07 Jan 2023 12:44:47 +0000
>
> We are recently experiencing test failures using Emacs 28, Emacs 27, and
> Emacs 26 on CI (non-interactively):
What about Emacs 29? Or is this report only about versions 28 and
older? In the latter case, why would it suddenly start failing, if
those versions are no longer being developed?
> https://builds.sr.ht/~bzg/job/918602
>
> 2 unexpected results:
> FAILED ob-octave/graphics-file ((should-not (buffer-live-p (get-buffer "*Org-Babel Error Output*"))) :form (buffer-live-p #<killed buffer>) :value t)
> FAILED ob-octave/graphics-file-space ((should-not (buffer-live-p (get-buffer "*Org-Babel Error Output*"))) :form (buffer-live-p #<killed buffer>) :value t)
>
> Note that (buffer-live-p #<killed buffer>) returns non-nil, which is
> unexpected.
Are you sure this is the right interpretation?
Anyway, is there any hope for a more self-contained recipe, which I
could try on my system without too much ado?
next prev parent reply other threads:[~2023-01-07 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 12:44 bug#60626: 30.0.50; `buffer-live-p' sometimes returns t on killed buffers Ihor Radchenko
2023-01-07 13:42 ` Eli Zaretskii [this message]
2023-01-07 15:01 ` Ihor Radchenko
2023-01-09 10:21 ` Michael Heerdegen
2023-01-11 11:08 ` Ihor Radchenko
2023-01-11 12:50 ` Eli Zaretskii
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=83ilhisbpg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60626@debbugs.gnu.org \
--cc=yantar92@posteo.net \
/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).