From: David Maus <dmaus@ictsoc.de>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: David Maus <dmaus@ictsoc.de>, emacs-orgmode@gnu.org
Subject: Re: FYI: Org mode testing framework, Emacs 23 and 22
Date: Sun, 18 Sep 2011 11:01:49 +0200 [thread overview]
Message-ID: <87y5xmmdfm.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <87bouinb12.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2242 bytes --]
At Sat, 17 Sep 2011 14:56:09 -0600,
Eric Schulte wrote:
>
> Hi David,
>
> >
> > For Emacs22 the only thing we need from simple.el is the definition of
> > special-mode; going to factor it out and trim it to Emacs22.
> >
>
> Sounds great, thanks.
Done. Conditionally defined in org-test.el when Emacs version = 22.
>
> >
> > With HEAD at dbf0e6d5bcbe94c8ee57d68889d3c25bf9cdef55 and a fix for
> > the check for featurep 'org (37db5deea5ef75186bb7413b196fa0c96e5bdfb9)
> > I got:
> >
>
> Thanks for compiling this information.
>
> >
> >
> > Selector: "\\(org\\|ob\\)"
> > Passed: 99
> > Failed: 10 (10 unexpected)
> > Total: 109/109
> >
> > Started at: 2011-09-16 06:56:59+0200
> > Finished.
> > Finished at: 2011-09-16 06:57:04+0200
> >
> > ......FF...................................................FF..F.F.......FF.................F..............F.
> >
> > F ob-fortran/list-var
> > Test real array input
> > (void-function characterp)
> >
> > F ob-fortran/list-var-from-table
> > Test real array from a table
> > (void-function characterp)
> >
>
> I've replaced the use of `characterp' in ob-fortran with integerp, which
> should be backwards-compatible with emacs22.
These errors are gone.
>
> >
> > F test-ob-exp/org-babel-exp-src-blocks/w-no-file
> > Testing export from buffers which are not visiting any file.
> > (wrong-type-argument stringp nil)
> >
> > F test-ob-exp/org-babel-exp-src-blocks/w-no-headers
> > Testing export without any headlines in the org-mode file.
> > (wrong-type-argument stringp nil)
> >
> > F test-ob-lob/export-lob-lines
> > Test the export of a variety of library babel call lines.
> > (wrong-type-argument stringp nil)
> >
>
> I have no idea what could be going wrong with these executions, would it
> be difficult to generate backtraces for these failures?
No, its really easy (as expected w/ Emacs): Section on interactive
debugging ERT mentions "b" to create the backtrace.
In case of w-no-file and w-no-headers `org-todo-line-regexp' is bound
to nil, in export-lob-lines `org-maybe-keyword-time-regexp' is bound
to nil. Backtraces are attached.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #1.2: test-ob-exp--org-babel-exp-src-blocks--w-no-headers.backtrace.gz --]
[-- Type: application/octet-stream, Size: 30134 bytes --]
[-- Attachment #1.3: test-ob-exp--org-babel-exp-src-blocks--w-no-file.backtrace.gz --]
[-- Type: application/octet-stream, Size: 30347 bytes --]
[-- Attachment #1.4: test-ob-lob--export-lob-lines.backtrace.gz --]
[-- Type: application/octet-stream, Size: 36557 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-09-18 9:02 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
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 [this message]
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=87y5xmmdfm.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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).