Re: sed tests

[Marco Wahl <marcowahlsoft@gmail.com>]

Hi Skip,

Collins <skip.collins@gmail.com> writes:

> Recently (last two or three weeks), when I run make test on the latest
> git source (currently release_9.1.6-395-g8ecc4c) on my mac with Emacs
> 26.0.90 (compiled with brew on my Mac), I get the following results:
>
> Ran 775 tests, 771 results as expected, 4 unexpected (2018-01-23 11:37:59-0500)
> 11 expected failures
>
> 4 unexpected results:
>    FAILED  ob-sed-test/cmd-line-header-argument
>    FAILED  ob-sed-test/in-file-header-argument
>    FAILED  ob-sed-test/simple-execution-of-script
>    FAILED  test-ob-python/session-multiline
>
> I would appreciate any suggestions for how to address the problem.
> This is not urgent, as I don't use ob-sed and org seems to be
> functioning normally otherwise. But OSX command line tools sometimes
> have quirks that show up as failed tests. Of course it is possible
> that I broke my emacs/org in some way.

Some days ago I accidentially saw that the sed tests were disabled and
that I could easily activate them.  And I did and thought that was a
wonderful idea.  And also the sed tests pass on my linux box.

This

> Test ob-sed-test/cmd-line-header-argument condition:
>     (ert-test-failed
>      ((should
>        (string= "A tested again file.
> "
> (with-temp-buffer ... ...)))
>       :form
>       (string= "A tested again file.
> "              "A test file.
> ")
>       :value nil))

shows that sed did not do the substitution of "test" by "tested again"
as defined in the respective sed babel block.

Maybe you could try to execute sed babel blocks directly.  Possibly you
get a better understanding of the behaviour.


HTH
   Marco