Ihor Radchenko writes:
> Jack Kamm writes:
>
>> Ihor Radchenko writes:
>>
>> ...
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=1eb598758980d5fa4d7bb21c98dfc56f42cae59a
>>
>> Please let me know whether the problem continues, or whether it seems to
>> improve.
>
> As soon as
Jack Kamm writes:
>> If we can (eventually) remove some custom code from Org and move it to
>> Emacs, it will be the best for working towards RMS request
>> https://orgmode.org/list/e1kiph1-0001lu...@fencepost.gnu.org
>
> I started down this path here:
>
>
Jack Kamm writes:
> Ihor Radchenko writes:
>
> ...
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=1eb598758980d5fa4d7bb21c98dfc56f42cae59a
>
> Please let me know whether the problem continues, or whether it seems to
> improve.
As soon as we fix CI :/ I think it is not
Ihor Radchenko writes:
>> 1. In addition to printing `org-babel-python-eoe-indicator' after
>>execution, we could also print out a "beginning of execution"
>>indicator before execution, and then capture the output between the
>>beginning and end indicators. This is how the async
Ihor Radchenko writes:
> We have fairly regular CI test failures for one of the ob-python tests.
> The test does not fail _every_ time, but I keep seeing the problem in
> various Emacs versions, including Emacs 29.
>
> Example log: https://builds.sr.ht/~bzg/job/1047678#task-build
>
> In the test
Jack Kamm writes:
> This one might take some time to fix, since it's hard to reproduce and
> I'm not sure the cause of it. But here are 3 different solutions I am
> considering now:
>
> 1. In addition to printing `org-babel-python-eoe-indicator' after
>execution, we could also print out a
Ihor Radchenko writes:
> Jack Kamm writes:
>
>>>FAILED 376/1256 test-ob-python/session-multiline (0.011955 sec) at
>>> ../lisp/test-ob-python.el:105
>>
>> Hmmm. Do you have an idea of how long this has been happening, and how
>> frequently it breaks?
>
> For months.
>
>> My first
Jack Kamm writes:
>>FAILED 376/1256 test-ob-python/session-multiline (0.011955 sec) at
>> ../lisp/test-ob-python.el:105
>
> Hmmm. Do you have an idea of how long this has been happening, and how
> frequently it breaks?
For months.
> My first suspicion is the large ob-python commit I
Ihor Radchenko writes:
> Hi,
>
> We have fairly regular CI test failures for one of the ob-python tests.
> The test does not fail _every_ time, but I keep seeing the problem in
> various Emacs versions, including Emacs 29.
>
> Example log: https://builds.sr.ht/~bzg/job/1047678#task-build
>
> In
Hi,
We have fairly regular CI test failures for one of the ob-python tests.
The test does not fail _every_ time, but I keep seeing the problem in
various Emacs versions, including Emacs 29.
Example log: https://builds.sr.ht/~bzg/job/1047678#task-build
In the test the result somehow includes
10 matches
Mail list logo
