On Wed, Jan 11 2023, Ihor Radchenko <yanta...@posteo.net> wrote: > Leo Butler <leo.but...@umanitoba.ca> writes: > >>>>>> Leo, could you please take a look? >>>>> >>>>> An earlier test is creating that *Org Babel Error Output* buffer. >>> >>> I will try to look into improving the tests so that we can trap the test(s) >>> that is(are) creating that error buffer. >> >> See the attachment. There are four test failures that are currently >> untrapped. I also see the `buffer-live-p' bug. > > It looks like `buffer-live-p' is not a bug, but rather the result of > backtrace being printed upon executing `kill-buffer' in unwind-protect > form from the test body: (1) test fails; (2) unwind-protect executes > kill-buffer; (3) backtrace is printed with "killed" buffer object.
Yes, that seems reasonable. > > So, the test failure is real. > > https://orgmode.org/list/94980226-d29a-4969-8640-1143a1979...@bundesbrandschatzamt.de > might be related. Ihor, How do you want to treat the patch that was included? I think we should have something like that to catch errors like these. And the failing tests should be marked as known failures (that need to be fixed, obviously). I note that both failures 3 & 4 are related to org's built-in features. Leo
