Leo Butler <leo.but...@umanitoba.ca> writes: >> 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.
Are you referring to "failures" in your attachment? I think that your expectation is wrong here. Org does not clear the "*Org-Babel Error Output*" buffer upon running next src block during Emacs session - it is a good thing when you run multiple src blocks and want to see the errors/warnings produced. So, if we want to do some definitive assertions about "*Org-Babel Error Output*", we could kill "*Org-Babel Error Output*" (if any) before running the test that checks this buffer. As for ob-octave failures, I suspect that octave throws some warnings on CI machine. I currently don't have podman setup to run CI tests locally - you may try to play with the problematic ob-octave tests to identify the problem as described in https://git.sr.ht/~bzg/org-mode-tests/ -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
