Re: [BUG] Failing tests for ob-clojure

Ihor Radchenko writes: >> I would love to write new tests but as I just started a new job >> and got a new baby at the same time, I don't think I'll find the >> time for it the next 3-4 month :( > > Understood. We are not in rush. It has been a while since the last activity in this thread.

Re: [BUG] Failing tests for ob-clojure

Ihor Radchenko writes: >> Unfortunately you're right and I would even say we can completely >> remove `test-ob-clojure.el`. >> There seems to be only tests for session support which currently >> doesn't exist anymore and another one which tests plain tangle >> and is not really Clojure

Re: [BUG] Failing tests for ob-clojure

Daniel Kraus writes: > Unfortunately you're right and I would even say we can completely > remove `test-ob-clojure.el`. > There seems to be only tests for session support which currently > doesn't exist anymore and another one which tests plain tangle > and is not really Clojure specific. Done.

Re: [BUG] Failing tests for ob-clojure

Hi! Ihor Radchenko writes: > I am now going through all the babel tests that are disabled by default. > > ob-clojure tests appear to be completely broken: > > 1. (org-test-for-executable "cider") assertion is strange as cider >package does not have any executable. > > 2. All the tests seems

[BUG] Failing tests for ob-clojure

Hi, I am now going through all the babel tests that are disabled by default. ob-clojure tests appear to be completely broken: 1. (org-test-for-executable "cider") assertion is strange as cider package does not have any executable. 2. All the tests seems to assert that ob-clojure supports

Re: Failing tests

Kévin Le Gouguec writes: > Kyle Meyer writes: > >>> I think I've narrowed this down to org-open-file running "less >>> examples/att1/fileA" instead of visiting this file. >> [...] >>> Let-binding org-file-apps to '(("." . emacs)) makes the tests pass, but >>> I don't know if that's the way we

Re: Failing tests

Kévin Le Gouguec writes: > Absolutely. I've attached a patch to that effect. I just realized that these let-bindings probably deserved explanatory comments. Here is an updated patch: >From f996ec3a10a845abae2fa463ab0ea7a761af1707 Mon Sep 17 00:00:00 2001 From:

Re: Failing tests

Kyle Meyer writes: >> I think I've narrowed this down to org-open-file running "less >> examples/att1/fileA" instead of visiting this file. > [...] >> Let-binding org-file-apps to '(("." . emacs)) makes the tests pass, but >> I don't know if that's the way we want to solve this. > > Thanks for

Re: Failing tests

Kévin Le Gouguec writes: > Thanks for the pointer, and for applying the patches! > FAILED ob-tangle/jump-to-org FAILED test-org-attach/dir I have had both tests failing for a while without understanding why, if this gets fixed as a side-effect of the incomplete fix I made for

Re: Failing tests (was: Possible fix for :includes header argument in org-babel C source blocks)

Kévin Le Gouguec writes: > Kyle Meyer writes: > >> The source for that page is in the worg repo: >> https://code.orgmode.org/bzg/worg/src/master/org-contrib/babel/languages/ob-doc-C.org > > Thanks for the pointer, and for applying the patches! > FAILED ob-tangle/jump-to-org FAILED

Failing tests (was: Possible fix for :includes header argument in org-babel C source blocks)

Kyle Meyer writes: > The source for that page is in the worg repo: > https://code.orgmode.org/bzg/worg/src/master/org-contrib/babel/languages/ob-doc-C.org Thanks for the pointer, and for applying the patches! >>> FAILED ob-tangle/jump-to-org >>> FAILED test-org-attach/dir > > :( > >

Re: Failing tests

Kyle Meyer writes: > Marco Wahl writes: > >> When building with "make test" I get >> >> #v+ >> 2 unexpected results: >>FAILED ob-tangle/jump-to-org >>FAILED test-org-attach/dir >> #v- >> >> does this ring a bell for anybody? > > FWIW I don't see either failure on my end (Emacs 26.3).

Re: Failing tests

Marco Wahl writes: > When building with "make test" I get > > #v+ > 2 unexpected results: >FAILED ob-tangle/jump-to-org >FAILED test-org-attach/dir > #v- > > does this ring a bell for anybody? FWIW I don't see either failure on my end (Emacs 26.3). Do they fail for you consistently?

Failing tests

Dear all, When building with "make test" I get #v+ 2 unexpected results: FAILED ob-tangle/jump-to-org FAILED test-org-attach/dir #v- does this ring a bell for anybody? Best regards, -- Marco

Re: [O] Backward incompatible outline-invisible-p change in emacs master for Org (Was: 6 failing tests on master branch)

On Wed, Jun 14, 2017 at 10:56 AM Kaushal Modi wrote: > One solution would be to have a new function "org-invisible-p" that > restores the old definition of outline-invisible-p. Interestingly I find > that an "org-invisible-p" did exist back then, but it was replaced with

[O] Backward incompatible outline-invisible-p change in emacs master for Org (Was: 6 failing tests on master branch)

On Thu, Jun 8, 2017 at 5:10 PM Nicolas Goaziou wrote: > > Test test-org/custom-properties condition: > > (ert-test-failed > > ((should > >(let > >(...) > > (org-test-with-temp-text "* H > > :PROPERTIES: > > :FOO: val > > :END: > > "

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 4:05 PM Nicolas Goaziou wrote: > Hello, > > Kaushal Modi writes: > > > Here's a patch rebased off maint (as it's just test and manual change > with > > edits to a backward compatible Tramp syntax). > > LGTM. > > Thank you. >

Re: [O] 6 failing tests on master branch

Hello, Kaushal Modi writes: > Here's a patch rebased off maint (as it's just test and manual change with > edits to a backward compatible Tramp syntax). LGTM. Thank you. Regards, -- Nicolas Goaziou0x80A93738

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 12:27 PM Nicolas Goaziou wrote: > AFAIU, the function doesn't need to change, but the manual needs to be > updated since, in (info "(org) External links") there is: > > /myself@some.where:papers/last.pdfsame as above > > which is no

Re: [O] 6 failing tests on master branch

Hello, Kaushal Modi writes: > Does org-export-file-uri need to change? Because now > > (org-export-file-uri "/ssh:myself@some.where:papers/last.pdf") > > returns > > "file://ssh:myself@some.where:papers/last.pdf" AFAIU, the function doesn't need to change, but the

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 12:02 PM Michael Albinus wrote: > Kaushal Modi writes: > > The stronger Tramp file name syntax requires now a method. Something > like "/ssh:myself@some.where:papers/last.pdf". This is backward > compatible with Emacs 25,

Re: [O] 6 failing tests on master branch

Kaushal Modi writes: > This seems to be related to a tramp file notation change on emacs > master. I don't use tramp, but I heard about it on emacs-devel. Indeed. > Here is a test expression: > > (find-file-name-handler "/myself@some.where:papers/last.pdf" >

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 10:26 AM Kaushal Modi wrote: > This one should be easy to debug since >> >> (org-export-file-uri "/myself@some.where:papers/last.pdf") >> >> is easy to reproduce. Could you investigate where the spurious "/" comes >> from? >> > > Will do. > This

Re: [O] 6 failing tests on master branch

On Thu, Jun 8, 2017 at 5:10 PM Nicolas Goaziou wrote: > > I remember reading that someone else too saw the fortran errors.. Is it > > because I don't have fortran on my system? > > No, I don't think so. OTOH, I have no idea about where this comes from. > Did little

Re: [O] 6 failing tests on master branch

Hello, Kaushal Modi writes: > 6 unexpected results: >FAILED ob-fortran/list-matrix-from-table1 >FAILED ob-fortran/list-matrix-from-table2 >FAILED ob-fortran/list-var-from-table >FAILED test-org-export/file-uri >FAILED test-org/custom-properties >

[O] 6 failing tests on master branch

Hello, I ran make test today using the latest version of org master branch (and latest of emacs master), and I see 6 failures: 6 unexpected results: FAILED ob-fortran/list-matrix-from-table1 FAILED ob-fortran/list-matrix-from-table2 FAILED ob-fortran/list-var-from-table FAILED