From: Eric Schulte <schulte.eric@gmail.com>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Collection of code block snippets
Date: Thu, 08 Sep 2011 09:16:01 -0600 [thread overview]
Message-ID: <87mxef6p4r.fsf@gmail.com> (raw)
In-Reply-To: m2bouwdxso.fsf@btinternet.com
Hi Martyn
Martyn Jago <martyn.jago@btinternet.com> writes:
> Hi Eric
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
> [...]
>
>>
>> I just made three small changes to the testing framework so it is now
>> possible to run the test suite in batch mode with the following.
>>
>> emacs -Q --batch -l path/to/org/testing/org-test.el --eval "(setq
>> org-confirm-babel-evaluate nil)" -f org-test-run-all-tests
>
> Great idea - unfortunately its not quite working for me since I get
> four failing tests. In addition I have no (easy) indication of which
> four tests are failing since the backtrace is just the output of the
> tests working (no backtrace for failed tests).
>
I'm getting four failing tests as well when I start Emacs with the -Q
option and no failing tests when I run it with my configuration loaded.
I will dig through my personal config, find out what options are making
these tests pass, and adjust the tests appropriately so that they all
pass with no personal config.
>
> This is what I like about the ert-run-batch commands - you get an
> indication and summary of tests passed, and the backtrace of any
> failures.
>
> Also, I mentioned that ert-batch.el and ert-run.el are not part of
> Emacs. This is actually because their contents were merged into ert.el
> within Emacs.
>
Thanks for mentioning the batch ert commands, I was not aware of their
existence. I've added a batch version of org-test-run-all-tests to the
org-mode test suite, the following should now be sufficient to run the
test suite from the command line with nicer output.
#+begin_src sh
emacs -Q --batch -l path/to/org/testing/org-test.el \
--eval "(setq org-confirm-babel-evaluate nil)" \
-f org-test-run-all-tests
#+end_src
Thanks -- Eric
>
> Regards
>
> Martyn
>
>>
>> Best -- Eric
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-09-08 15:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 16:35 [babel] Collection of code block snippets Eric Schulte
2011-09-05 8:29 ` Rainer M Krug
2011-09-05 16:54 ` Eric Schulte
2011-09-06 8:26 ` Rainer M Krug
2011-09-06 15:16 ` Eric Schulte
2011-09-06 15:35 ` Martyn Jago
2011-09-06 17:13 ` Eric Schulte
2011-09-07 8:19 ` Rainer M Krug
2011-09-07 18:24 ` Martyn Jago
2011-09-07 18:15 ` Martyn Jago
2011-09-08 15:16 ` Eric Schulte [this message]
2011-09-08 16:18 ` Martyn Jago
2011-09-08 17:44 ` Eric Schulte
2011-09-08 18:34 ` Martyn Jago
2011-09-08 22:03 ` Martyn Jago
2011-09-09 8:22 ` Rainer M Krug
2011-09-09 10:58 ` Martyn Jago
2011-09-09 11:11 ` Martyn Jago
2011-09-09 20:39 ` Eric Schulte
2011-09-10 8:09 ` Martyn Jago
2011-09-11 20:57 ` Eric Schulte
2011-09-14 4:49 ` David Maus
2011-09-14 12:10 ` Martyn Jago
2011-09-09 19:19 ` Eric Schulte
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mxef6p4r.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=martyn.jago@btinternet.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).