From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ob-lilypond test failures
Date: Sun, 13 Sep 2015 15:27:15 -0400 [thread overview]
Message-ID: <8737yii0h8.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 878u8a4665.fsf@gmx.us
Rasmus <rasmus@gmx.us> writes:
> Hi,
>
> I get lilypond errors when running make test now and I didn't see any old
> messages about this.
>
> The errors persists even after installing lilypond.
>
> For ob-lilypond/ly-attempt-to-open-pdf:
>
> pdf-info-query: epdfinfo: Error opening /home/rasmus/src/code/org-mode/testing/examples/ob-lilypond-test.pdf:No such file or directory
>
> For ob-lilypond/ly-attempt-to-play-midi:
>
> Test failed: ((should (equal "No midi file generated so can't
> play!" (org-babel-lilypond-attempt-to-play-midi midi-file))) :form
> (equal "No midi file generated so can't play!" "No midi file generated
> so can’t play!") :value nil :explanation (array-elt 29
> (different-atoms (39 "#x27" "?'") (8217 "#x2019" "?’"))))
>
> I don't know anything about lilypond. I can make the tests not run when
> lilypond is not present, but as said, they don't even seem to work when
> lilypond is present. I installed version 2.18.2.
>
> Thanks,
> Rasmus
I get passes:
,----
| ...
| passed 65/587 ob-lilypond/feature-provision
| passed 66/587 ob-lilypond/ly-arrange-mode
| No pdf file generated so can't display!
| passed 67/587 ob-lilypond/ly-attempt-to-open-pdf
| No midi file generated so can't play!
| passed 68/587 ob-lilypond/ly-attempt-to-play-midi
| passed 69/587 ob-lilypond/ly-check-for-compile-error
| ...
`----
but I didn't go any further to try to figure out who is producing
the messages.
I have lilypond installed.
Org-mode version 8.3.1 (release_8.3.1-234-g8c85c9 @
/home/nick/elisp/org-mode/lisp/)
--
Nick
prev parent reply other threads:[~2015-09-13 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 16:48 ob-lilypond test failures Rasmus
2015-09-13 19:27 ` Nick Dokos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737yii0h8.fsf@pierrot.dokosmarshall.org \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.