emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: FYI: Org mode testing framework, Emacs 23 and 22
Date: Sun, 11 Sep 2011 15:02:08 -0600	[thread overview]
Message-ID: <87aaaaokpq.fsf@gmail.com> (raw)
In-Reply-To: 877h5f558c.wl%dmaus@ictsoc.de

>
> The test result with failing tests for Emacs23 is attached.
>
> ,----
> | Passed: 101
> | Failed: 8 (8 unexpected)
> | Total:  109/109
> |
> | Started at:   2011-09-11 19:53:46+0200
> | Finished.
> | Finished at:  2011-09-11 19:53:51+0200
> `----
>
> 7 of the 8 are fortran-tests, the 8th is
> `org-babel-get-inline-src-block-matches'.
>

I would imagine that the fortran tests are failing because you do not
have the gfortran executable in your path.  I had to apt-get install
fortran for these tests to pass.

The eighth test should not be passing.  I've getting all tests passing
on Emacs24.

>
>>
>> Once we have all tests running for Emacs>=22 it would be very nice (and
>> not too difficult) to add a post-update hook to the Org-mode git
>> repository which could run the test suite and record the results for
>> every version of Emacs with something like the following
>>
>> emacs23 -Q --batch -l $ORGTESTSTUFF --eval "
>> (progn (org-test-run-all-tests)
>>        (htmlize-buffer)
>>        (write-file "commit-id-23.html"))"
>
> +1
>

I suppose the next step here would be to talk to Bastien about setting
up such a system on the org-mode server.

Cheers -- Eric

>
> Best,
>   -- David
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  reply	other threads:[~2011-09-11 21:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02  4:47 FYI: Org mode testing framework, Emacs 23 and 22 David Maus
2011-09-02 13:50 ` Eric Schulte
2011-09-11 18:00   ` David Maus
2011-09-11 21:02     ` Eric Schulte [this message]
2011-09-13  3:50       ` David Maus
2011-09-13 14:48         ` Eric Schulte
2011-09-14  4:10           ` David Maus
2011-09-16  5:01           ` David Maus
2011-09-17 20:56             ` Eric Schulte
2011-09-18  9:01               ` David Maus
2011-09-22 13:44                 ` Eric Schulte
2011-09-25  7:30                   ` David Maus
2011-09-18  9:05               ` David Maus
2011-09-18  9:07               ` David Maus
2011-09-18 14:46               ` David Maus
2011-10-21 18:46       ` Bastien
2011-10-21 18:57         ` Sebastien Vauban
2011-10-22 16:19           ` Eric Schulte
2011-10-23 17:56             ` Bastien
2011-10-24 12:12             ` Sebastien Vauban
2011-10-25 13:25               ` Brian Wightman
2011-10-25 17:40                 ` Martyn Jago
2011-11-09 21:22                   ` Eric Schulte
2011-11-09 21:50                     ` Samuel Wales
2011-11-09 22:20                       ` Eric Schulte
2011-09-11 18:01   ` David Maus
2011-09-11 20:31     ` Martyn Jago

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=87aaaaokpq.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=dmaus@ictsoc.de \
    --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 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).